Awesome
<div id="top"></div> <!-- *** Thanks for checking out the Best-README-Template. If you have a suggestion *** that would make this better, please fork the repo and create a pull request *** or simply open an issue with the tag "enhancement". *** Don't forget to give the project a star! *** Thanks again! Now go create something AMAZING! :D --> <!-- PROJECT SHIELDS --> <!-- *** I'm using markdown "reference style" links for readability. *** Reference links are enclosed in brackets [ ] instead of parentheses ( ). *** See the bottom of this document for the declaration of the reference variables *** for contributors-url, forks-url, etc. This is an optional, concise syntax you may use. *** https://www.markdownguide.org/basic-syntax/#reference-style-links --> <!-- [![Forks][forks-shield]][forks-url] [![Stargazers][stars-shield]][stars-url] --> <!-- [![MIT License][license-shield]][license-url] --> <!-- [![LinkedIn][linkedin-shield]][linkedin-url] --> <!-- PROJECT LOGO --> <br /> <div align="center"> <a href="https://github.com/Lodestone-Team/client"> <img src="readme/lodestone_logo.svg" alt="Logo" width="80" height="80"> </a> <h3 align="center">Lodestone</h3> <p align="center"> Client for the Lodestone project <br /> <a href="https://beta.lodestone.cc/"><strong>Website(Beta WIP) »</strong></a> <br /> <br /> <!-- <a href="https://github.com/github_username/repo_name">View Demo</a> --> · <a href="https://github.com/Lodestone-Team/client/issues">Report Bug</a> · <a href="https://github.com/Lodestone-Team/client/issues">Request Feature</a> </p> </div> <!-- ABOUT THE PROJECT -->!!Repo Deprecated!!
This repo is functionally deprecated in favour of the new mono repo: https://github.com/Lodestone-Team/lodestone
However, due to Lodestone CLI still pointing to this repo to fetch the latest releases, this repo is not archived.
Built With
<!-- * [![Node.js][Node.js]][Node.js-url] --> <!-- * [![Express][Express]][Express-url] --> <p align="right">(<a href="#top">back to top</a>)</p>Getting Started (end user)
You should not download Lodestone Core directly due to its lack of ability to self-update. Please use Lodestone CLI instead.
Using Docker Image
As of v0.4.3 we have added Docker support to lodestone core.
Our precompiled images will be based on the newest release available from: ghcr.io/lodestone-team/lodestone_core
.
Alternatively, you may build your own image using the default Dockerfile
, not additional arguments required.
Note You may add additional ports as you wish to forward, but 16662 is the default port served in the image. You may add a volume for your lodestone instance to be accessible, in the example below, you can create a volume first by using
docker volume create lodestone
.
Docker CLI example:
docker run -d \
--name lodestone \
--restart unless-stopped \
-p 16662:16662 \
-v lodestone:/home/user/.lodestone \
ghcr.io/lodestone-team/lodestone_core
Docker Compose example:
Download the docker-compose.yml file from this repo using
wget https://raw.githubusercontent.com/Lodestone-Team/lodestone_core/main/docker-compose.yml
and then run it using
docker compose up -d
Alternatively, create docker-compose.yml yourself:
version: '3.8'
services:
lodestone:
container_name: lodestone
image: ghcr.io/lodestone-team/lodestone_core
restart: unless-stopped
ports:
- "16662:16662"
volumes:
- lodestone:/home/user/.lodestone
volumes:
lodestone:
<!-- GETTING STARTED -->
Getting Started (development)
Please make sure you have cargo
and rustc
, for instruction on how to install the Rust toolchain, see here: rustup.rs.
Prerequisites
These instructions apply to Ubuntu 20.04 LTS and later.
build-essential
is required for the Rust toolchain.sudo apt-get install build-essential
pkg-config
andlibssl-dev
are required to compile Axumsudo apt-get install pkg-config libssl-dev
cpuidtool
is required to query CPU information
A few other packages are needed to compile Lodestonesudo apt-get install cpuidtool libcpuid-dev
sudo apt-get install libffi-dev libmagic-dev file
Installation
Running the client
- Clone the repo
git clone https://github.com/Lodestone-Team/client
- By default Lodestone stores its data in
~/.lodestone
. If you would like to override it for development & testing please define theLODESTONE_PATH
environment variable to override it.export LODESTONE_PATH=~/test_dev
- Running
cargo run --bin main
Contributing
Contribution is welcome, please join our Discord for more details.
<p align="right">(<a href="#top">back to top</a>)</p> <!-- LICENSE -->License
This project uses the GNU Affero General Public License v3.0. See our LICENSE files for details. For an alternate (commercial) license, please raise an issue.
<p align="right">(<a href="#top">back to top</a>)</p> <!-- CONTACT --> <!-- ## Contact Your Name - [@twitter_handle](https://twitter.com/twitter_handle) - email@email_client.com Project Link: [https://github.com/github_username/repo_name](https://github.com/github_username/repo_name) <p align="right">(<a href="#top">back to top</a>)</p> --> <!-- ACKNOWLEDGMENTS -->Credits
Active members of the Lodestone client team:
- Peter Jiang (CheatCod) - Lead Developer
- Kevin Huang (Ynng) - Developer
- Mark Sun (Lemonsity) - Developer