Hey all, I have an app I'm working on that's open source, and backed to github. Because of this, I don't want to commit passwords and usernames to github.The problem arises by the fact that the code you upload to ep.io is read-only. Does anyone use ep.io and have any suggestions on how to configure settings? I want to be able to connect via `epio run bash` and edit settings after deployed. Thanks, Anthony Ford, KF5IBN, Research Assistant, Center for Advanced Radio Astronomy, University of Texas at Brownsville ford.anthonyj@gmail.com
Perhaps you should use environment variables?
How to on ep.io: https://www.ep.io/docs/epioini/#id13
And you can export them on your local machine, and read them:
export PASSWORD='mypassword'
And of course, in your application:
PASSWORD = os.environ.get("PASSWORD")
Jack
On Wed, Jan 25, 2012 at 3:24 PM, Anthony Ford <ford.anthonyj@gmail.com>wrote:
> Hey all,
> I have an app I'm working on that's open source, and backed to github.
> Because of this,
> I don't want to commit passwords and usernames to github.The problem
> arises by the
> fact that the code you upload to ep.io is read-only.
>
> Does anyone use ep.io and have any suggestions on how to configure
> settings?
> I want to be able to connect via `epio run bash` and edit settings after
> deployed.
>
> Thanks,
> Anthony Ford,
> KF5IBN,
> Research Assistant,
> Center for Advanced Radio Astronomy,
> University of Texas at Brownsville
> ford.anthonyj@gmail.com
>
>
Problem with that is to be able to upload the environment vars, you need to have them in your epio.ini file, which needs to be committed to your repo to be deployed. Anthony Ford, KF5IBN, Research Assistant, Center for Advanced Radio Astronomy, University of Texas at Brownsville ford.anthonyj@gmail.com On Wed, Jan 25, 2012 at 17:52, Jack Pearkes <jackpearkes@gmail.com> wrote: > Perhaps you should use environment variables? > > How to on ep.io: https://www.ep.io/docs/epioini/#id13 > > And you can export them on your local machine, and read them: > > export PASSWORD='mypassword' > > And of course, in your application: > > PASSWORD = os.environ.get("PASSWORD") > > Jack > > On Wed, Jan 25, 2012 at 3:24 PM, Anthony Ford <ford.anthonyj@gmail.com>wrote: > >> Hey all, >> I have an app I'm working on that's open source, and backed to github. >> Because of this, >> I don't want to commit passwords and usernames to github.The problem >> arises by the >> fact that the code you upload to ep.io is read-only. >> >> Does anyone use ep.io and have any suggestions on how to configure >> settings? >> I want to be able to connect via `epio run bash` and edit settings after >> deployed. >> >> Thanks, >> Anthony Ford, >> KF5IBN, >> Research Assistant, >> Center for Advanced Radio Astronomy, >> University of Texas at Brownsville >> ford.anthonyj@gmail.com >> >> >
On Jan 25, 2012, at 19:08 , Anthony Ford wrote: > Problem with that is to be able to upload the environment vars, you need to have them in your epio.ini file, which needs to be committed to your repo to be deployed. Actually, if there is an `epio-{appname}.ini` file in your repository (where appname is the name of this particular app instance, i.e. `epio-myapp.ini` if your app is at myapp.ep.io), settings defined in it - including environment variables - will override those from `epio.ini`. You can put the secrets in there, and simply not check the -{appname} version into git. > Anthony Ford, > KF5IBN, > Research Assistant, > Center for Advanced Radio Astronomy, > University of Texas at Brownsville > ford.anthonyj@gmail.com Regards, Matthew Frazier http://leafstorm.us/
Oh, so the epio.ini file does not need to be committed to the repo? Wow, that needs to be clearer in the docs. Anthony Ford, KF5IBN, Research Assistant, Center for Advanced Radio Astronomy, University of Texas at Brownsville ford.anthonyj@gmail.com On Wed, Jan 25, 2012 at 18:27, Matthew Frazier <leafstormrush@gmail.com>wrote: > On Jan 25, 2012, at 19:08 , Anthony Ford wrote: > > Problem with that is to be able to upload the environment vars, you need > to have them in your epio.ini file, which needs to be committed to your > repo to be deployed. > > Actually, if there is an `epio-{appname}.ini` file in your repository > (where appname is the name of this particular app instance, i.e. > `epio-myapp.ini` if your app is at myapp.ep.io), settings defined in it - > including environment variables - will override those from `epio.ini`. You > can put the secrets in there, and simply not check the -{appname} version > into git. > > > Anthony Ford, > > KF5IBN, > > Research Assistant, > > Center for Advanced Radio Astronomy, > > University of Texas at Brownsville > > ford.anthonyj@gmail.com > > Regards, > Matthew Frazier > http://leafstorm.us/ >
Right, it only uses Git as the transport layer. It won't ignore files in gitignore. I actually take advantage of this by gitignoring the entire 'instance' directory where my local config/data files are so they're not in the repo. Epio will still upload them. I only found this by accident. The docs mention it only indirectly <https://www.ep.io/docs/client/#upload> by introducing its own '.epioignore' file. On Wed, Jan 25, 2012 at 7:29 PM, Anthony Ford <ford.anthonyj@gmail.com>wrote: > Oh, so the epio.ini file does not need to be committed to the repo? > > Wow, that needs to be clearer in the docs. > > Anthony Ford, > KF5IBN, > Research Assistant, > Center for Advanced Radio Astronomy, > University of Texas at Brownsville > ford.anthonyj@gmail.com > > > > On Wed, Jan 25, 2012 at 18:27, Matthew Frazier <leafstormrush@gmail.com>wrote: > >> On Jan 25, 2012, at 19:08 , Anthony Ford wrote: >> > Problem with that is to be able to upload the environment vars, you >> need to have them in your epio.ini file, which needs to be committed to >> your repo to be deployed. >> >> Actually, if there is an `epio-{appname}.ini` file in your repository >> (where appname is the name of this particular app instance, i.e. >> `epio-myapp.ini` if your app is at myapp.ep.io), settings defined in it >> - including environment variables - will override those from `epio.ini`. >> You can put the secrets in there, and simply not check the -{appname} >> version into git. >> >> > Anthony Ford, >> > KF5IBN, >> > Research Assistant, >> > Center for Advanced Radio Astronomy, >> > University of Texas at Brownsville >> > ford.anthonyj@gmail.com >> >> Regards, >> Matthew Frazier >> http://leafstorm.us/ >> > >
Anthony, Have you tried Heroku? They allow you to store configuration variables outside of SCM with environment variables. http://devcenter.heroku.com/categories/python -- Kenneth Reitz On Wednesday, January 25, 2012 at 7:08 PM, Anthony Ford wrote: > Problem with that is to be able to upload the environment vars, you need to have them in your epio.ini file, which needs to be committed to your repo to be deployed. > > Anthony Ford, > KF5IBN, > Research Assistant, > Center for Advanced Radio Astronomy, > University of Texas at Brownsville > ford.anthonyj@gmail.com (mailto:ford.anthonyj@gmail.com) > > > On Wed, Jan 25, 2012 at 17:52, Jack Pearkes <jackpearkes@gmail.com (mailto:jackpearkes@gmail.com)> wrote: > > Perhaps you should use environment variables? > > > > How to on ep.io (http://ep.io): https://www.ep.io/docs/epioini/#id13 > > > > And you can export them on your local machine, and read them: > > > > export PASSWORD='mypassword' > > > > And of course, in your application: > > > > PASSWORD = os.environ.get("PASSWORD") > > > > Jack > > > > On Wed, Jan 25, 2012 at 3:24 PM, Anthony Ford <ford.anthonyj@gmail.com (mailto:ford.anthonyj@gmail.com)> wrote: > > > Hey all, > > > I have an app I'm working on that's open source, and backed to github. Because of this, > > > I don't want to commit passwords and usernames to github.The problem arises by the > > > fact that the code you upload to ep.io (http://ep.io) is read-only. > > > > > > Does anyone use ep.io (http://ep.io) and have any suggestions on how to configure settings? > > > I want to be able to connect via `epio run bash` and edit settings after deployed. > > > > > > Thanks, > > > Anthony Ford, > > > KF5IBN, > > > Research Assistant, > > > Center for Advanced Radio Astronomy, > > > University of Texas at Brownsville > > > ford.anthonyj@gmail.com (mailto:ford.anthonyj@gmail.com) > > >
I've been including my epio.init files in the gitignore file, trying to separate deployment from source code as much as possible. On Wed, Jan 25, 2012 at 7:16 PM, Kenneth Reitz <me@kennethreitz.com> wrote: > Anthony, > > Have you tried Heroku? They allow you to store configuration variables > outside of SCM with environment variables. > > http://devcenter.heroku.com/categories/python > > -- > Kenneth Reitz > > On Wednesday, January 25, 2012 at 7:08 PM, Anthony Ford wrote: > > Problem with that is to be able to upload the environment vars, you need > to have them in your epio.ini file, which needs to be committed to your > repo to be deployed. > > Anthony Ford, > KF5IBN, > Research Assistant, > Center for Advanced Radio Astronomy, > University of Texas at Brownsville > ford.anthonyj@gmail.com > > > > On Wed, Jan 25, 2012 at 17:52, Jack Pearkes <jackpearkes@gmail.com> wrote: > > Perhaps you should use environment variables? > > How to on ep.io: https://www.ep.io/docs/epioini/#id13 > > And you can export them on your local machine, and read them: > > export PASSWORD='mypassword' > > And of course, in your application: > > PASSWORD = os.environ.get("PASSWORD") > > Jack > > On Wed, Jan 25, 2012 at 3:24 PM, Anthony Ford <ford.anthonyj@gmail.com>wrote: > > Hey all, > I have an app I'm working on that's open source, and backed to github. > Because of this, > I don't want to commit passwords and usernames to github.The problem > arises by the > fact that the code you upload to ep.io is read-only. > > Does anyone use ep.io and have any suggestions on how to configure > settings? > I want to be able to connect via `epio run bash` and edit settings after > deployed. > > Thanks, > Anthony Ford, > KF5IBN, > Research Assistant, > Center for Advanced Radio Astronomy, > University of Texas at Brownsville > ford.anthonyj@gmail.com > > > > >