Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fig #6

Merged
merged 3 commits into from
Oct 22, 2014
Merged

Fig #6

merged 3 commits into from
Oct 22, 2014

Conversation

vidarl
Copy link
Member

@vidarl vidarl commented Oct 15, 2014

Renamed images to be fig compatible and added a Fig configuration

In fig it is not possible to have settings ( like installation_type=composer|tarball ) in a separate file, so everything is placed inside fig.yml.. Fig does support getting configuration values from environment variables, but I opt'ed not to use that

FYI : Containers will not be named the same by Fig vs Vagrant. ( You cannot fully control the naming when using Fig, only in vagrant )

@vidarl
Copy link
Member Author

vidarl commented Oct 15, 2014

Ready for review

### Access your eZ Publish installation

When the containers are created, you should be able to browse to eZ Publish setup wizard by going to http://localhost/:8080

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"følge feil", but I guess this should be http://localhost:8080/

@andrerom
Copy link
Contributor

+1

Possible followup could be:

  • reusing this in vagrant config (but for now coreos does not have fig right?)
  • alternative fig config with cluster like setup (but within one machine)

@vidarl
Copy link
Member Author

vidarl commented Oct 22, 2014

Correct, fig is not part of coreos ATM

@vidarl vidarl closed this Oct 22, 2014
@vidarl vidarl reopened this Oct 22, 2014
vidarl added a commit that referenced this pull request Oct 22, 2014
@vidarl vidarl merged commit 14424bc into master Oct 22, 2014
@vidarl vidarl deleted the fig branch October 22, 2014 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants