Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/f0rkb0mbz/heroku_container_registry
This repository demonstrates how to use heroku as a container hosting platform with Docker and a simple NodeJs app.
https://github.com/f0rkb0mbz/heroku_container_registry
Last synced: 13 days ago
JSON representation
This repository demonstrates how to use heroku as a container hosting platform with Docker and a simple NodeJs app.
- Host: GitHub
- URL: https://github.com/f0rkb0mbz/heroku_container_registry
- Owner: f0rkb0mbZ
- Created: 2020-02-29T18:55:37.000Z (almost 5 years ago)
- Default Branch: master
- Last Pushed: 2022-12-12T03:10:01.000Z (about 2 years ago)
- Last Synced: 2023-08-05T13:42:04.944Z (over 1 year ago)
- Language: HTML
- Size: 39.1 KB
- Stars: 1
- Watchers: 0
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
## Hello there!
This is a simple node app running on heroku!
## Hosted App
This app is hosted here 👉 [herokudock.herokuapp.com](https://herokudock.herokuapp.com/)
## How to Deploy
1. Install [Heroku CLI](https://devcenter.heroku.com/articles/heroku-command-line).
2. Login
```bash
$ heroku login
```
3. Login to Container Registry
You must have Docker set up locally to continue. You should see output when you run this command.
```bash
$ docker ps
```
4. Now you can sign into Container Registry.
```bash
$ heroku container:login
```
5. Push your Docker-based app
Build the Dockerfile in the current directory and push the Docker image.
```bash
$ heroku container:push web -a
```
6. Deploy the changes
Release the newly pushed images to deploy your app.
```bash
$ heroku container:release web -a
```
## Available Scripts
In the project directory, you can run:
### `npm start`
Runs the app in the development mode.
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
### `npm test`
Launches the test runner in the interactive watch mode.
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.
### `npm run build`
Builds the app for production to the `build` folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.
### `npm run eject`
**Note: this is a one-way operation. Once you `eject`, you can’t go back!**
If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.