Silcrate 0.2.6

What's New

• Silcrate runs on container 1.2.2. It's the version Silcrate checks for during setup and the one it installs for you — if you're still on 1.2.0, setup will prompt you to update. Nothing you've already created changes: containers, images, volumes and networks carry over untouched.
• Containers hit memory limits less often. The 1.2.2 runtime gives each container's virtual machine more headroom for memory mappings, so workloads that map a lot of files — databases, search indexes, big test suites — stop failing on a machine that has memory to spare.

Silcrate 0.2.5

Fixes

• The update prompt no longer interrupts launch. Silcrate now waits until the app has finished opening before checking for a new version, so the update alert appears over the app itself instead of the splash screen.

Silcrate 0.2.4

What's New

• Passwords and tokens no longer sit in plain sight. Anything that looks like a credential — by its name, or by the shape of its value — is now drawn dotted out. Click the eye to reveal it, and it hides itself again the moment the view redraws, so nothing lingers on screen after you look away. Everything that isn't a secret stays readable as before.
• Copy a hidden value without revealing it. Right-click a masked entry and copy the real value straight to the clipboard.
• Masking follows your secrets everywhere they show up. A running container's environment, each Compose service's environment, an image's baked-in environment, labels on containers, volumes and networks, and volume mount options — including the password on a CIFS mount — all hide credentials the same way.

Fixes

• A label or environment entry that has a key but no value now displays as written, instead of picking up a stray =.

Silcrate 0.2.3

What's New

• Passwords and tokens no longer sit in plain sight. Anything that looks like a credential — by its name, or by the shape of its value — is now drawn dotted out. Click the eye to reveal it, and it hides itself again the moment the view redraws, so nothing lingers on screen after you look away. Everything that isn't a secret stays readable as before.
• Copy a hidden value without revealing it. Right-click a masked entry and copy the real value straight to the clipboard.
• Masking follows your secrets everywhere they show up. A running container's environment, each Compose service's environment, an image's baked-in environment, labels on containers, volumes and networks, and volume mount options — including the password on a CIFS mount — all hide credentials the same way.

Fixes

• A label or environment entry that has a key but no value now displays as written, instead of picking up a stray =.

Silcrate 0.2.2

What's New

• The launch animation is smoother. The falling-glyph splash now draws off the main thread and does far less work per frame, so startup stays fluid instead of stuttering.

Fixes

• You'll hear about new versions while setting up, too. The update check only ran once you reached the main window, so anyone still configuring the container engine never learned a newer Silcrate was out. It now runs on that first setup screen as well.

Silcrate 0.2.1

What's New

• Updates show up the same day they ship. Silcrate now checks for new versions every hour instead of once a day, so you're not sitting on an old build waiting for it to notice.
• Opening About checks for an update. The check runs quietly in the background — if you're already current, nothing appears.

Fixes

• The domain you register during setup is now actually the default. If the previously stored default wasn't routing anywhere, Silcrate switches to the one you just set up. A default that already routes is left alone, since you picked that one on purpose.

Silcrate 0.2.0

What's New

• A DNS screen, under Networking. Every domain this Mac routes, which one is the default, and for each of them the containers answering there — with their service, project and hostname. Add a domain, make one the default, or remove one you no longer need. A domain can't be removed while it's the default or still in use, and the screen tells you what to do first. Making a different domain the default only affects containers created from then on: nothing restarts, and nothing already running is renamed.

• Hostnames open in your browser. Click one in the DNS screen, in a network's attached containers, or on a container's or machine's Overview.

• Setup registers a domain for you. A new step on the checklist sets the domain new containers are created under. It's pre-filled, so the fast path is one click, and it shows what your container names will look like as you type. Names are checked before the password prompt — .local, reserved names, real top-level domains and names another tool already uses each explain what taking them would break. If you'd rather do it by hand, the exact command is shown and follows whatever you type.

• Already set up on an earlier version? You'll be sent back to setup once to register a domain. Nothing else about your install changes.

• Register a domain in Terminal and Silcrate picks it up, without reopening anything.

• The sidebar is grouped. Dashboard on top, then Workload, Resources, Networking and Build under their own headings, replacing the unlabelled dividers. Networks and DNS appear for machines too, since a machine attaches to the same networks and answers on the same domains a container does.

• One icon set, everywhere. Containers, machines, images, volumes and networks look the same on page headers, empty states, create screens, dashboard tiles and attachment tables.

• Setup tells you which version you have. The command-line tool and guest kernel rows read "Installed 1.2.3" rather than just "Installed".

Fixes

• Adding a domain that's already routed is refused up front, instead of quietly doing nothing.
• During setup, typing a domain you've already registered counts as done — no password prompt, no error.

Silcrate 0.1.12

What's New

• Silcrate runs on container 1.2.0. It's the version Silcrate checks for during setup and the one it installs for you — if you're still on 1.1.0, setup will prompt you to update. Kernels are now checked against an expected checksum before they're installed.

• Container and machine names are capped at 63 characters. That's the limit container 1.2.0 enforces, and the name field flags a name that's too long as you type. If you already have a container or machine with a longer name, 1.2.0 will refuse to start, delete or show logs for it — remove it before you update.

Fixes

• No more restarting the app after first-run setup. Setting Silcrate up on a Mac with no container CLI left Builder, Containers, Machines and Networks reporting "Connection invalid", and quitting and reopening was the only way out. Those screens now reconnect on their own, whenever the service is installed, restarted or replaced.

• A rejected name tells you the whole rule. The error under the name field listed which characters were allowed but never the length, so a name that was too long came back with advice you were already following. Containers and machines now say 2 to 63 characters, networks up to 63, volumes up to 255 — and a network name says it must be lowercase and start and end with a letter or digit.

Silcrate 0.1.11

What's New

• Silcrate shows what every item is doing. Start, stop, or restart a container, machine, image, volume, or network and the row now spins and names the action in place of its status — a restarting machine reads as restarting instead of flashing a blank "Stopped" that looked like a failure. Run an action across a whole selection and the selection summary counts the progress down, instead of going quiet until the final result.

• The menu bar reports failures instead of swallowing them. Starting or stopping something from the menu bar popover used to fail silently. Now the row spins while it works, a failed action shows a card with the reason and Retry / Dismiss, and a row that's already working won't fire the same command a second time.

Fixes

• Stopping the engine service now looks like it's stopping. The sidebar, dashboard, and menu bar kept reading "Running" with a live Stop button through the entire shutdown. They now show a stopping state and wait for the service to actually stop before calling it done.

• CPU usage stays believable. The dashboard and menu bar now measure CPU against the number of cores your Mac has, so it no longer climbs past 100%. The same container also reads the same percentage everywhere — no more 45.3% in one place and 45% in another — and percentages now follow your region's number format.

• Settings comes to the front. Opening Settings from the menu bar popover now brings its window forward, instead of leaving it behind whatever you were working in.

• Rows stop jumping. A container or machine row no longer shifts its title sideways the moment a command starts and back when it finishes.

• A machine's mounts are colored like a container's. A bind mount into your Mac's own storage now stands out on the machine screen the same way it does on the container screen, instead of blending in.

• Resetting a running build warns you first. The reset confirmation now tells you it will stop the build before resetting, when the build is up.

• The menu bar item stays on after setup. Finishing first-run setup no longer left the menu bar item switched off.

Silcrate 0.1.10

What's New

• Compose stacks. A new Compose section lists your stacks — running, partly up, or stopped, with drift and orphans flagged per row. Open one for its services, its network and volumes, the compose file read-only with unsupported lines struck through, and every service's logs interleaved into one timeline.

• Delete confirmations tell you what they will do. What goes, what survives, how much space comes back, what breaks. Irreversible deletes gate on a typed phrase — selectable, with a Copy button. Same dialog everywhere: containers, machines, images, volumes, networks, stacks.

• A deletion takes what it can. Select twelve, the eight that are free are deleted and the three still in use are named and skipped, instead of the whole action refusing.

• Long errors stay until read. They stick as a toast with a close button; auto-dismiss pauses while you hover or leave the window. Repeats collapse into one with a count.

• CPU and memory are picked with steppers, bounded by what your Mac can give. Free-text size fields gone. Create forms open on your configured defaults instead of hardcoded numbers.

• The log console is selectable. Drag, Select All, Copy, Find. Holds 10,000 lines, won't trim while you're scrolled up.

• Search sits above the list it filters, not in the titlebar.

• Cancel a running build — or a stack launch, keeping what it already created.

Fixes

• Confirming a stack delete now actually deletes the stack.
• Failed commands say why they failed.
• A failed service start no longer reports success.
• Image names with a registry port parse correctly; untagged images show <none>.
• Names are checked against the rule the engine will apply.
• Sizes read the same on every screen.
• Update preferences stick across launches.