unit9 / gae-secure-scaffold-python Goto Github PK

The setup and build process is tied so closely with Vagrant, it's practically impossible to deploy without using it.

This is a severe issue if you consider:

• automating builds / deploys via CI
• people that can't run Vagrant for any reason (bugs, unsupported platform, etc)
• debugging the process

Currently the model seems to be:

• Work happens on a feature/* branch
• PR to merge to develop
• ... merge to master - when?

I would argue that this model is broken:

• There's no clear indicator of when changes on develop should propagate to master
• There's no CI or CD system in place, and we're not tying the branching model with GAE deployments, (there are no deployments at all actually), so the condition of "merging to master = deploy live" does not apply
• It creates confusion because Github allows only one "default" branch - if it's "master", then all PRs land on master by default. If it's develop, all we've achieved is we've renamed "master" to "develop" and master will end up being 7441 commits behind 90% of the time.

I would suggest we adopt a simple model where each feature branch is merged directly to master after a review. It works extremely well on the Cookbook.

@maciejzasada @krzysztofnowak discuss.

On behalf of @dominicberzins:

• During development, projects should never be visible to the general public; e.g. login with a valid @unit9.com (or - configurable whitelist) GApps account must be required
• During testing/QA, this protection must be bypassed while testing sharing on social media (Facebook, G+, Twitter, etc). - these bots can't input a password

Make the mechanism secure and flexible.

This:

Instal required Vagrant plugins
$ vagrant plugin install vagrant-host-shell

is not required. vagrant up does it automatically.

On Windows 8 Git CMD when I enter vagrant up I get the following:

After a few minutes, I get a timeout message:

Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If I manually launch Oracle VM VirtualBox Manager, I see that the VM is running and asking for login and password.

I enter vagrant / vagrant and I am through, but it is a dead end.
There is nothing there:

And I still can't ssh:

• Do we really need Ansible?
• Can we make it simple, robust, fast?