### Background
Newer upstream PostgreSQL Docker images, now require a password for use. If you were previously using passwordless access to a PostgreSQL DB, it will likely fail with an error.
This linked GitHub issue showcases the error:
https://github.com/docker-library/postgres/issues/681
### Solution
The postgres docker page gives instructions on how to use the new image : https://hub.docker.com/_/postgres
There seems to be two different options we can take here :
Option 1 - Implement a password using the environment variable
Option 2 - Revert back to old behavior of having no password requirement
### Thoughts
Based on the team members remark it looks like increased security was the major reason for this breaking changing happening in a minor update. Refer to this comment : https://github.com/docker-library/postgres/issues/681#issuecomment-586517154
As such I opted to use Option 1 here in this change as increased security of a DB is generally a win for every one in most cases.
Unfortunately, the only reliable way to create internal links
is to use relative links to other Markdown files. This does
match the way links on GitHub work, but makes it harder to
create these links.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Fix incorrect links in compose section
there's a bug causing wrapped links to not work, and replacing
some links to point to the .md file, so that IDE's can check
if the anchors are valid. Also replaced some links to point
to their new location.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* engine/swarm: update links
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* Fix various broken links
There's a bug in the "jekyll-relative-links" plugin that causes wrapped links to not work.
Also replacing some links to point to the .md file, so that IDE's can check if the anchors
are valid. Finally, replaced some links to point to their new locations, so that users don't
get redirected..
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
It occupied me quite a while figuring out why this sample didn't have a restart policy. And why we where supposed to always properly stop the containers wheres you normally would simply hit `Ctrl+C`.
Turned out that this `pid` issue is a rails-specific issue. https://github.com/docker/compose/issues/1393#issuecomment-99988242
And of course there's already [a Gem for fixing that](https://github.com/lorenzosinisi/shutup) but having the one-liner in the `docker-compose.yml` keeps the logic where it belongs to (and now also is treated here in the sample).
* Reword lots of instances of 'will'
* Reword lots of instances of won't
* Reword lots of instances of we'll
* Eradicate you'll
* Eradicate 'be able to' type of phrases
* Eradicate 'unable to' type of phrases
* Eradicate 'has / have to' type of phrases
* Eradicate 'note that' type of phrases
* Eradicate 'in order to' type of phrases
* Redirect to official Chef and Puppet docs
* Eradicate gratuitous 'please'
* Reduce use of e.g.
* Reduce use of i.e.
* Reduce use of N.B.
* Get rid of 'sexagesimal' and correct some errors
Without the host and credentials, the `myapp_test` database is not
created, and instead, the user receives a PG error and a long backtrace.
This commit moves the credentials to a default anchor to share across
development and test environments.
* added example for env_file variables
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* copyedits and rework of Compose rails example
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* updated/improved Compose samples
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* linked some more basic docker-compose commands
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* coypedit
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* improve Compose rails sample
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* updated file list and commands based on feedback for no skip-bundle
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added, start, stop, rebuild info to Rails sample
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* updated info re: default Flask port for compose get started
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* more changes for rebuilding steps
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added rebuild info
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* added info about Gemfile.lock to rebuild steps
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
* Update to Rails 5, Ruby 2.3.3, remove therubyracer
Update packages to latest versions. The actual nodejs is installed on line 18. Changed to a general comment regarding the need to rebuild images when adding gems.
* update rails welcome screenshot to 5.0.0.1
In this example, database.yml uses the default value of `postgres` for the `database` key.
The database postgres is normally not used for user data, but for administrative purposes. This means people following this example will not be able to drop the database, and in general it's just not a great idea.
Usha Mandya
Aravind
Sebastiaan van Stijn
Sebastiaan van Stijn
charliemenke
paigehargrave
Maria Bermudez
Maria Bermudez
Norman Kämper-Leymann
newoneforasn4
Oscar Caballero
Takahiro Naito
schalkwijk
Misty Stanley-Jones
jottr
Jon-Michael Deldin
Victoria Bialas
Kasidesh Yontaradidthaworn
Hugo
Tarun Chinmai
Marko Schulz
Adam Stevenson
Ryan Ore
Misty Stanley-Jones
Victoria Bialas
Jonas Friedmann
Gaetan
John Mulhausen