-
Notifications
You must be signed in to change notification settings - Fork 44
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* SeAT 3.0 Documenation * Starting Documentation on SeAT 3.0 with Dev-Setup * SeAT 3.0 Documenation * Removing 3.0 from Logo * SeAT 3.0 Documentation * adapting to latest docker-commands
- Loading branch information
1 parent
000a0a1
commit 68428c9
Showing
1 changed file
with
17 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,23 +1,25 @@ | ||
![SeAT](http://i.imgur.com/aPPOxSK.png) | ||
|
||
Getting a development installation up and running is now even easier than before. Simply download the `seat` tool (if you havent already), and run `seat install:development`! | ||
Getting a development installation up and running is now even easier than before. | ||
SeAT 3.0 will be profit from the extensive functionality of `docker-compose`. | ||
Simply download the latest dev-docker files, run `bash prepare-source.sh` and finally `docker-compose up -d`. | ||
|
||
|
||
## installation | ||
|
||
1. `curl -fsSL https://git.io/vXb0u -o /usr/local/bin/seat` | ||
2. `chmod +x /usr/local/bin/seat` | ||
3. `seat install:development` | ||
1. ` git clone https://github.com/eveseat/scripts.git /var/seat` | ||
2. `cd /var/seat/docker-compose-dev` | ||
3. `bash prepare-source.sh` | ||
4. `docker-compose --project-name seat-dev up -d` | ||
|
||
In order to have a running test-enviroment you must create an Application on | ||
[CCP-Developers](https://developers.eveonline.com/). Select all esi-scopes and save `EVE_CLIENT_ID` and | ||
`EVE_CLIENT_SECRET` in `.env`. | ||
|
||
## usage | ||
|
||
This command also accepts an optional path specification for the installation. For example: | ||
you can now access your Dev-Enviroment via port 8080: `http://localhost:8080`. | ||
|
||
``` | ||
$ seat install:development --destination ~/code/seat-dev | ||
Using /usr/bin/git for git | ||
Using /usr/bin/unzip for unzip | ||
Using /usr/local/bin/composer for composer | ||
Using /usr/local/bin/php for php | ||
Cloning Main SeAT repository to ~/code/seat-dev... | ||
``` | ||
## helpful stuff | ||
|
||
## manual development setup | ||
If you dont want to use the `seat` tool to configure a development project for you, then you can refer to the following page for more information on a reccomended development environment setup for SeAT: [General Development](development/general/). | ||
1. If you need access to console (f.e. to run `php artisan`) you can access it via `docker exec -it seat-app sh` |