Skip to content

[WIP] Add development environment#1825

Closed
kasparsd wants to merge 15 commits intoampproject:developfrom
kasparsd:add/1823-dev-env
Closed

[WIP] Add development environment#1825
kasparsd wants to merge 15 commits intoampproject:developfrom
kasparsd:add/1823-dev-env

Conversation

@kasparsd
Copy link
Copy Markdown

Fixes #1823.

  • Use Docker containers defined in docker-compose.yaml running inside Vagrant for better hostname isolation (enables http://ampwp.local).

  • Document system requirements and setup.

@googlebot
Copy link
Copy Markdown

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

@googlebot googlebot added the cla: no Has not signed the Google CLA label Jan 17, 2019
@kasparsd
Copy link
Copy Markdown
Author

I signed it!

@googlebot
Copy link
Copy Markdown

CLAs look good, thanks!

@googlebot googlebot added cla: yes Signed the Google CLA and removed cla: no Has not signed the Google CLA labels Jan 17, 2019
@westonruter
Copy link
Copy Markdown
Member

This is interesting. I'm very novice with Docker, but we've recently using https://github.com/felixarntz/wordpressdev as the environment to do development on, at least a few of us. It's also based on Docker, though it doesn't require putting Docker configuration in the repo as it just uses whatever environment it finds itself in. I know that Gutenberg has a Docker setup, but I haven't used it. I'm not very good to review this.

/cc @felixarntz

@felixarntz
Copy link
Copy Markdown
Collaborator

I would generally advise against putting a dev environment into a specific project's repository. IMO this plugin should provide the tools needed to develop for it (via NPM and Composer), but it should be agnostic about which dev environment to use.

If there is consensus that a specific dev environment for the AMP plugin makes sense, it should be a separate repository, that could be linked to from the readme for example.

@kasparsd
Copy link
Copy Markdown
Author

Thanks for the feedback @felixarntz!

The idea behind a simplified development environment was to simplify the effort required for new developers to contribute to the project. For example, running phpunit currently requires a development machine with a full WP setup and files in particular locations. Having a minimal development environment with the suggested defaults could significantly reduce the time it takes to start contributing to the project.

A separate repo sounds like a good solution!

@kasparsd kasparsd closed this Jan 18, 2019
@kasparsd kasparsd deleted the add/1823-dev-env branch January 18, 2019 11:51
@kasparsd kasparsd restored the add/1823-dev-env branch January 18, 2019 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes Signed the Google CLA

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants