You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm picking up a fork which has been dormant for awhile and trying to get it into a production state, but there's something I don't quite get. I'm able to build and startup the development system with the standard commands:
$ bin/dev-servers development.ini --app-name app --clear --init --load
# In a separate terminal, make sure you are in the encoded-venv
$ bin/pserve development.ini
Now I want to point it to a production Postgres, it's running on another machine and managed by our DB group, but I haven't been able to figure out how to do that. It keeps wanting to start up postgres itself. I've tried using production.ini instead but that doesn't seem to work either. I also tried modifying the buildout.cfg with a full postgres connection string, but it still seems to create a local db in /tmp/snovault
Is there something I'm missing?
The text was updated successfully, but these errors were encountered:
I'm picking up a fork which has been dormant for awhile and trying to get it into a production state, but there's something I don't quite get. I'm able to build and startup the development system with the standard commands:
Now I want to point it to a production Postgres, it's running on another machine and managed by our DB group, but I haven't been able to figure out how to do that. It keeps wanting to start up postgres itself. I've tried using
production.ini
instead but that doesn't seem to work either. I also tried modifying thebuildout.cfg
with a full postgres connection string, but it still seems to create a local db in /tmp/snovaultIs there something I'm missing?
The text was updated successfully, but these errors were encountered: