jaspero/cli

CLI Tool for JMS

cli's Issues

Ask for IAM Service Account Credentials API

• When setting up JMS with jaspero jms init let's put a step in where we ask the user to enable the IAM Service Account Credentials API.
  The link should look something like this: https://console.cloud.google.com/apis/library/iamcredentials.googleapis.com?project=[projectId]
• Lets also ask him to set up the Cloud Datastore Import Export Admin role. We could maybe do this with the cli as well. https://github.com/Jaspero/jms/wiki/Common-Tasks#custom-services-for-modules

Update for jms master branch remuval

Creating web hosting

When creating a static or blog app from jms init we should also either automatically configure a new firebase site (if possible through the cli) called [project-id]-web or we should ask the user to configure it before moving forward.

Ask for basic theme adjustments

When setting up a new jms project let's ask the user to make basic theme adjustments. The six things that come to mind.

1. Change primary theme color
2. Change accent theme color
3. Change logo
4. Change favicon
5. Ask for sidebar position
6. In the background we should automatically change the email background color and logo.

JMS: Prompt for creating initial admin user

We need to ask for creating an initial user. This needs to happen at the very last step after function deployment so that all the right things trigger.

1. What email address do you want to use?
2. What password do you want to use?

Prompt to deploy functions

This is particularly useful because of how we have automated deployment configured to only trigger functions for files that changed initial deployment doesn't trigger functions and this has to happen manually every time

Setting up blog or static set up ghtoken

When setting up blog or static with jms init we need instruct the user to set up github personal access token and ask for it. Then we need to add it to firebase config under ghtoken.

Check for CLI updates on each run

Prompt to deploy Firebase Functions

Upon successful execution of setup (Step Run Setup script?), prompt once again with Do you want to run initial deploy of Firebase Functions?.
If true, using fs enter directory {projectName}/functions and run:

• npm i
• npm run deploy

Change the title of the cms

When running jms init we should change the title of the app in index.html

Create secrets through cli

We should create a FIREBASE_TOKEN repository secret when running jms init. Additionally if it's static or blog we should also create a SERVICE_ACCOUNT.

https://docs.github.com/en/rest/actions/secrets#create-or-update-a-repository-secret

Edit package.json

In jms init we should replace all of the jms references in package.json with the projects references.
Additionally we should ask if releases are necessary (default to no) and remove all of that if it isn't needed.

Prompt to Enable Auth on Firebase Project

Prompt to Enable Billing on Firebase Project

Error: HTTP Error: 400, Billing account for project 'projectId' is not found. Billing must be enabled for activation of service(s) 'cloudbuild.googleapis.com,containerregistry.googleapis.com' to proceed.

Prompt to deploy Firestore rules

Add changelog

Dynamic Collections replaced

We don't currently replace dynamic-collections.const.ts when a new flavor/blog is initiated

Command for generating Module

jaspero jms generate module

With predefined templates like:

• blank (just exported object with typings and empty schema, layout, definitions)
• full (including many examples)

cool but not too useful (more for docs):

• user (basic user fields)
• blog