Compare commits
2 commits
| Author | SHA1 | Date | |
|---|---|---|---|
| 14c9acaeb6 | |||
| 4c0cbb86c1 |
3 changed files with 141 additions and 8 deletions
131
CHANGELOG.md
Normal file
131
CHANGELOG.md
Normal file
|
|
@ -0,0 +1,131 @@
|
|||
# Changelog
|
||||
|
||||
What changed in each released version, for people running the app rather than
|
||||
building it. `git pull && docker compose up -d` in your clone picks up the tag
|
||||
named here.
|
||||
|
||||
Schema changes apply themselves at startup. Where a release needs you to do
|
||||
something — back up `data/app.db`, re-authorize a character, load new game data
|
||||
— it says so under **Before you upgrade**.
|
||||
|
||||
---
|
||||
|
||||
## 0.6.0
|
||||
|
||||
The industry planner learns what your planets and your factories are actually
|
||||
doing, and the sidebar becomes yours to arrange.
|
||||
|
||||
### Before you upgrade
|
||||
|
||||
- **Re-authorize every character.** This release reads your industry skills, to
|
||||
show how many job slots each character has and how many are free. Growing the
|
||||
permission list does not upgrade the access you have already granted, so until
|
||||
a character goes through **Add a character** on `/characters` again, its slot
|
||||
counts read *unknown* — everything else keeps working.
|
||||
- Nothing else. No destructive migration, no game-data reload.
|
||||
|
||||
### A page for your jobs in progress
|
||||
|
||||
**Industry jobs** is a new page: every character's undelivered jobs, split into
|
||||
Manufacturing, Science and Reaction — the three slot pools the game gives you —
|
||||
and grouped by character.
|
||||
|
||||
Each character's line says how many slots are used, how many they have and how
|
||||
many are free, read from their trained skills. Each job shows a progress bar with
|
||||
a live countdown, its run count, the blueprint, the facility, and when it ends in
|
||||
EVE time. A job that has finished but not been delivered still shows, still
|
||||
counted against the slot it is holding — because it is.
|
||||
|
||||
### Your planets, as they are now rather than as EVE last wrote them down
|
||||
|
||||
EVE works planetary industry out lazily. When the app asks for a colony, the
|
||||
answer describes it as of the last time the game bothered to update it — which
|
||||
can be a day ago. The game client hides this by simulating forward; the app used
|
||||
to show you the raw figure, so a launchpad full of product read as empty.
|
||||
|
||||
It now does the same simulation, and every planet says which of three things it
|
||||
is doing:
|
||||
|
||||
- **Producing**, with what is ready to collect, what is still to come out of the
|
||||
inputs already up there, and a live countdown to when those inputs run out.
|
||||
- **Out of inputs** — its factories are running and there is nothing left to feed
|
||||
them.
|
||||
- **Waiting** — its factories had already stopped before the game last looked,
|
||||
and it says how long ago that was.
|
||||
|
||||
Each character's heading carries the longest of their running timers, so you can
|
||||
see at a glance when you next have to go round, or **Finished** when none of
|
||||
their planets is still running.
|
||||
|
||||
The planner uses the same figures. What a planet has made counts as stock, the
|
||||
inputs those cycles ate no longer do, and the product the inputs still up there
|
||||
will become is counted as on its way — so it plans the next run against what will
|
||||
be there, not against a day-old snapshot.
|
||||
|
||||
### Planets get sent whole loads
|
||||
|
||||
A shipping list is now rounded up to a quantity every factory on the planet can
|
||||
use evenly. Sending 688 cycles to 22 factories left the last one short; it now
|
||||
sends a whole number of cycles each, and a 2-input planet also shows the exact
|
||||
half that goes to each of its two sets of eleven. Both figures copy when you
|
||||
click them.
|
||||
|
||||
There is also a new setting, **Minimum job length** (default 48 hours): a load is
|
||||
sized to keep the planet busy at least that long rather than for the four hours
|
||||
the need alone might call for, because a trip to a planet costs the same whatever
|
||||
it carries. Launchpad space and what is actually in your hangar both still cap
|
||||
it, and the page says which one decided.
|
||||
|
||||
When there is not enough to go round, the planets serving the top of your build
|
||||
list are loaded first.
|
||||
|
||||
### A sidebar you can arrange
|
||||
|
||||
**Config** gains a Menu section. Every entry takes a name, an icon and a position,
|
||||
and you can create folders and put entries in them. A folder opens by itself when
|
||||
you are on a page inside it. Icons are Font Awesome names — `house`, `atom`,
|
||||
`route` — and a name the app does not recognise is refused rather than silently
|
||||
drawn as nothing.
|
||||
|
||||
The sidebar now collapses to a rail on every page, not only the dense ones.
|
||||
|
||||
### The watchlist tells you how to build the row
|
||||
|
||||
On the Industry Watchlist, the two invention tables put the decryptor — and the
|
||||
relic, on T3 — under the item name, and add the run count the invented blueprint
|
||||
is good for. Every row gains **add to Planned**, which writes that row as a build
|
||||
line into the Planned box on the Industry Plan: the right runs, the right
|
||||
decryptor, the right relic, without retyping any of it.
|
||||
|
||||
---
|
||||
|
||||
## 0.5.0
|
||||
|
||||
The Industry Plan becomes the centre of the app. Build list, Planned and In stock
|
||||
feed one plan whose blocks expand into the job tree behind each line; priority
|
||||
flows from the build list through the reaction and PI planners; everything to buy
|
||||
lands on one page instead of two half-lists. Adds a maximum job length, invents
|
||||
Tech II components rather than pricing them as if you could build them, tracks
|
||||
and prices every material a recipe consumes instead of only the bottom of the
|
||||
tree, and ships a dark mode.
|
||||
|
||||
## 0.4.0
|
||||
|
||||
The home page becomes a dashboard — procurement, jobs by slot pool, PI and
|
||||
reaction coverage. Planned builds raise the PI and reaction targets, and the
|
||||
build list reserves the stock it takes so two pages stop planning the same units.
|
||||
Adds a market-orders page that flags your undercut and outbid orders.
|
||||
|
||||
## 0.3.1
|
||||
|
||||
Fixes found by walking through a fresh install.
|
||||
|
||||
## 0.3.0
|
||||
|
||||
Makes the app somebody else's as well as its author's: one Configuration page for
|
||||
every tunable, the production region derived from the system you pick rather than
|
||||
hardcoded, a button to load the game data, and a login gate.
|
||||
|
||||
## 0.2.0
|
||||
|
||||
First published image.
|
||||
16
README.md
16
README.md
|
|
@ -111,14 +111,15 @@ schedule.
|
|||
|
||||
Go to **Configuration**. The order matters — later steps depend on earlier ones.
|
||||
|
||||
1. **Production system.** Search for the system you build in. This is the one
|
||||
setting that decides your production *region*, which is where the app prices
|
||||
what you make and which market Procurement compares against. Nothing that
|
||||
involves selling works until it is set.
|
||||
1. **Market region.** Search for the region you sell in. This is where the app
|
||||
prices what you make and which market Procurement and Orders compare
|
||||
against. Nothing that involves selling works until it is set.
|
||||
2. **Contact address**, under General. Sent to ESI and mokaam.dk in the
|
||||
User-Agent to identify you as the operator. **Data refuses to fetch anything
|
||||
until this is set** — it is not optional.
|
||||
3. **Staging systems**, if you stage separately from where you build.
|
||||
3. **Hub systems**: every system you build, react or stage in. The app stores
|
||||
all of your assets wherever they are, but the planners count only stock
|
||||
sitting in a hub. Anything else shows on Stock as "outside hubs".
|
||||
4. **The panels that apply to you** — Routing (your haulers, hulls, jump skills
|
||||
and courier rate), Industry (taxes, fees, assumed ME), Reactions, Planetary
|
||||
industry, Procurement, LP. Every field explains what it means and what it
|
||||
|
|
@ -155,8 +156,9 @@ git pull
|
|||
docker compose up -d
|
||||
```
|
||||
|
||||
`git pull` brings the new image tag and the release notes together. Schema
|
||||
changes are applied automatically at startup.
|
||||
`git pull` brings the new image tag and the release notes together — see
|
||||
[CHANGELOG.md](CHANGELOG.md) for what each version added and whether it needs
|
||||
anything from you. Schema changes are applied automatically at startup.
|
||||
|
||||
**Back up `data/app.db` first when the release notes say a migration is
|
||||
destructive.** Most upgrades can be rolled back by checking out the previous
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ services:
|
|||
# a release can carry a one-way database migration, so upgrading is
|
||||
# something you do deliberately (`git pull`), not something a restart does
|
||||
# to you.
|
||||
image: forge.narog.fr/eve-assistant/app:0.5.0
|
||||
image: forge.narog.fr/eve-assistant/app:0.7.0
|
||||
restart: unless-stopped
|
||||
ports:
|
||||
# Host port from .env, so a port clash does not force you to edit this
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue