To get started with Hamster PaaS, follow the steps below:
- Prepare your environment file: You will need to create a
.env
file in the root directory of the project. You can find an example file named.env.example
in the repository. Copy and rename this file to.env
, and update the necessary fields according to your configuration.
Here is an example of the contents of the .env
file:
# GIN_MODE=release
PORT=9898
MEILI_SEARCH="http://127.0.0.1:7700"
NGINX_LOG_PATH=./compose/nginx/log/access.log
MYSQL_DATABASE=aline
MYSQL_USER=aline
MYSQL_PASSWORD=changeme
MYSQL_ROOT_PASSWORD=changeme
MYSQL_HOST=127.0.0.1
MYSQL_PORT=3306
ALINE_DB_USER=root
ALINE_DB_PASSWORD=changeme
ALINE_DB_HOST=127.0.0.1
ALINE_DB_PORT=30303
ALINE_DB_NAME=aline
FROM_EMAIL=
EMAIL_PASSWORD=
- Start Docker containers: Run the following command in the terminal to start the required Docker containers:
docker-compose up -d
This command will start all the necessary services, such as database and search engine, in the background.
- Run the application: Finally, execute the following command to start the Hamster PaaS application:
go run .
The application should now be up and running. You can access the Hamster PaaS dashboard by navigating to http://localhost:9898
in your browser.
Hamster is aiming to build the one-stop infrastructure developer toolkits for Web3.0. It defines itself as a development, operation and maintenance DevOps service platform, providing a set of development tools as well as O&M tools, empowering projects in Web3.0 to improve their coding and delivery speed, quality and efficiency, as well as product reliability & safety.
With Hamster, developers or project teams realize the development, verification and O&M stages of their blockchain projects in an automatic, standardized and tooled approach: from contract template of multiple chains, contract/frontend code build, security check, contract deployment to the contract operation and maintenance.
Together with its developer toolkits, Hamster offers the RPC service and decentralized computing power network service when users choose to deploy their contracts via Hamster.
At the same time, the contract security check part within the developer toolkits is offered separately to its to-C customers, who could check their contracts to avoid potential security risks.
This project exists thanks to all the people who contribute.