|Kevin Hoerr 909cf65c97||1 year ago|
|migrations/00000000000000_diesel_initial_setup||2 years ago|
|src||1 year ago|
|.env.sample||1 year ago|
|.gitignore||1 year ago|
|.travis.yml||1 year ago|
|Cargo.toml||1 year ago|
|Dockerfile||2 years ago|
|LICENSE||3 years ago|
|README.md||1 year ago|
|diesel.toml||2 years ago|
August Offensive is a game as a web service that enables players to achieve world domination in turn-based strategy. Players as Allegiances can generate armies, gain control of regions, and defeat their enemies. The Allegiance that controls all of the regions around the world claims victory of the August Offensive.
The main goal of August Offensive is to enable players to interact with the service only when they are available to do so. Effectively, players do not need to maintain connection to the service for the entirety of the game. To prevent games from deadlocking, a customary time limit is enforced (ex. 96 hours).
The project is built using the Rust programming language, actix-web as the web framework, and Diesel for interacting with a PostgreSQL database. Diesel and actix-web work on stable Rust, removing the constant need to support nightly features. In addition, Diesel provides a client that makes it easy to migrate between schemas as they evolve between releases. This helps the project maintain a great level of portability without putting too great pressure on the application code.
The front-end of this project will be written using Elm (although this is subject to change). Development on the front-end portion will not begin until August Offensive's web API has reached relative stability. The target version number for stability is 1.0.0.
Visit the Wiki for guides detailing how to deploy August Offensive (e.g. standalone or using Docker).
While the project is still getting off the ground, there is not much back-end of which to build off. That doesn't mean you can't help brainstorm at least! There is much about the core functionality that is still up in the air at this point. Please have a look at the Roadmap for a detailed layout of intended features and / or milestones.