< Home

Project creation is managed but the script wov-init. What a time to be alive. This requires you pick a few options before running the script.

• Pick a Project Name and Code - Project name (PROJECTNAME} is the one-word name for this project: ex. nodejs. PROJECTCODE is a short reference to this, probably 3-4 characters. ex. njs.
• Create Your Own Git Repo in your Server - ex. in AWS CodeCommit. You will be propted for this.

Run wov-init

It will propt you for several bits of information. At the conclusion, you should have a functioning WovTools project. It's pretty bare bones, so you need to modify some variables to make it work.

Common Configs To Your Project

Database

WovTools has little respect for Kubernetes clusters. We expect them to come and go. Databases however are forever. So, we don't put them in the cluster's VPC, but the default. If you destroy your custer, your data will persist. Because of this you need to set up a peered connection to access your database easily.

NOTE: I am working on a script to create this, but peered connections are a pain to set up. For now, see the wov-cmd mkdb script in alywan project.

wovtools/config.json

See wovtools config files.

Create a Cluster

See Cluster Creation.