opscrew 0.1.0 → 0.1.1

package/LICENSE

@@ -187,7 +187,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright [yyyy] [name of copyright owner]
+   Copyright 2026 Mihailo Popović
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

package/NOTICE

@@ -1,5 +1,5 @@
 OpsCrew
-Copyright 2026 The OpsCrew Authors
+Copyright 2026 Mihailo Popović
 
 This product is licensed under the Apache License, Version 2.0 (see LICENSE),
 except for the contents of the ee/ directory, which are licensed under the

package/README.md

@@ -1,6 +1,4 @@
-# OpsCrew
-
-**The ops crew you didn't hire.**
+<p align="center"><img src="https://raw.githubusercontent.com/softzer0/opscrew/main/.github/assets/opscrew-header.png" alt="OpsCrew: the ops crew you didn't hire" width="100%"></p>
 
 From a GitHub repo to a hardened production deployment on your own cloud. Any cloud. You keep the infrastructure code.
 
@@ -26,6 +24,8 @@ Where it deploys:
 - **A server you already have, shared by several OpsCrew apps if you like:** see [Deploy to a server you already have](https://docs.opscrew.dev/own-server/).
 - **A Portainer you already run, for example on a NAS:** see [Deploy to a Portainer you already run](https://docs.opscrew.dev/portainer-target/). OpsCrew can also add [Portainer](https://docs.opscrew.dev/portainer/) to a server as a web UI for your containers.
 - **Your own computer, with the same production stack in your Docker:** see [Your app's production stack on your own computer](https://docs.opscrew.dev/localhost/). No server, no cloud account and no domain needed.
+- **Cloudflare, with no server, for static and server-rendered sites:** see [Host your site on Cloudflare](https://docs.opscrew.dev/cloudflare-hosting/). Free for static files.
+- **GitHub Pages, for static sites in public repositories:** see [Publish your site on GitHub Pages](https://docs.opscrew.dev/github-pages/). Free, without custom headers or commercial use.
 
 One app can have several environments, such as dev on your computer, staging on a small server and prod on the live one, and a tested image moves to prod unchanged: see [dev, staging and prod](https://docs.opscrew.dev/environments/). Deploy jobs can also run on the server itself or on your computer: see [Self-hosted runners](https://docs.opscrew.dev/runners/).
 
@@ -67,6 +67,8 @@ Run these in your app's repository, in order:
 
 To install it once instead of fetching it with `npx` each time, run `npm install -g opscrew`, then `opscrew init`, `opscrew analyze` and so on.
 
+In Claude Code, the OpsCrew plugin runs the same steps from the chat, and every plan still waits for your approval: `/plugin marketplace add softzer0/opscrew`, then `/plugin install opscrew@opscrew`. See [the plugin's README](https://github.com/softzer0/opscrew/tree/main/plugin).
+
 ## After the first deploy
 
 - `npx opscrew destroy` deletes the deployment's infrastructure. It asks you to type the server name first and can take a snapshot.