projectx | off the shelf infrastructure | Code Editor library

Your "workspaces" property in package.json looks right. I'm using NPM Workspaces and it's working well, but it's still missing a lot of features so you need to wire things up yourself. I also don't think npm worksace is a command (but maybe for the future?), so here's a checklist to get it to work:

• Make sure you're using Node 15+ and NPM 7+
• Set all package.json to "private": true,
• Delete all package-lock.json inside of your project, go to the root, then npm install. It should generate one root level package-lock.json that contains all dependencies for your workspaces
• Since you're using npm-run-all, add this to your scripts:

It doesn't have a general specified meaning. This is just a way for Git to display an abbreviated path when the whole thing would break screen formatting.

When you run docker run with the -it flag it will run the container and give you a shell into it. So the root@ad02e79cfb5b:/# you were seeing was the prompt inside the docker container (root is the user, ad02e79cfb5b is the host name and / means you are in the root folder).

To get back into it you first need to know if the container is still running. To achieve this run docker ps -a (not the thant the -a flag is important as without it you will only see running containers and not stopped ones).

If the container you ran is still running then note the id and run docker exec -it /bin/bash to get a shell back to it.

If the container is stopped then I would suggest removing it docker rm and re-running it (docker run -it ...).

It seems like the api that the package uses is broken, I am having the same issue. Also if you go to https://api.ratesapi.io the website doesn't load.

It should be as simple as

Usually, the Maven POM is both build POM and consumer POM. This is not ideal, and will probably change in future versions of Maven.

At the moment, your best option seems to be the flatten Maven plugin, which allows you to remove "unnecessary" parts of the POM before uploading it.

It's fairly simple: you need to enable the domains that your app uses.

The two domains you have are the defaults for cases where you have a common domain:

• www.yourdomain.com/* is the custom domain that you typically share out with people.
• projectx.firebaseapp.com is the default domain generated by Firebase, and is typically also used in sign-in screens (although you can change this).

You may also want to add:

• projectx.web.app, which is a newer default domain that Firebase creates. But this is not required, so only add it if you expect to hand it out to folks.
• localhost, which is handy for local testing

Have a look at this github issue: https://github.com/docker/compose/issues/2120

There are two options to set the COMPOSE_PROJECT_NAME. Use the -p commandline flag or the COMPOSE_PROJECT_NAME environment variable. Both are documented here: https://docs.docker.com/compose/reference/overview/#compose-project-name

When you run docker-compose, it needs a project name for the containers. If you don't specify the -p option, docker-compose looks for an environment varaible named COMPOSE_PROJECT_NAME. If both are not set, it defaults to the current working directory. Thats the behaviour you have.

If you don't want to add a commandline parameter, you can specify the environment variable in your .env file inside the directory of your docker compose file. See https://docs.docker.com/compose/env-file/

Use Hangfire, it's Background Methods functionality is great, and provides you with a nice dashboard for free: https://docs.hangfire.io/en/latest/background-methods/index.html