Juni 2023 - Seite 31 von 33 - Cloud Computing Köln

Since its debut last December, we’ve been improving WordPress.com Newsletter to meet the needs of writers and creators everywhere. Now we’re introducing a big update — the ability to add paid subscriptions and premium content, whatever plan you’re on. Including the Free plan.

Here’s the deal — you can now kickstart your newsletter without spending a penny, build your audience, and then add paid subscriptions into the mix at any point. It’s a great way to explore the shape of your newsletter without paying upfront while giving your readers a way to support your work at any point along the way. If you want to keep on growing, our paid plans provide lower transaction fees and all the features you need to manage and scale your newsletter and website.

Let your readers fuel your creativity

Paid subscriptions let your fans support your art, writing, or project directly. Once your creativity has captivated your audience, there’s a good chance some of them will gladly give something back by supporting your work financially.

And it’s not an all-or-nothing game. You can still put out free posts to grow your readership, enable one-time tips and donations, or keep some of your content exclusive to subscribers.

Take more creative control

We’re all about giving writers and creators the power and flexibility to do things their own way.

From selecting beautiful visual themes, customizing them to make everything feel more like you, or turning your newsletter into a full-fledged website or store, you’ll save time, cut costs, and have a bunch fewer logins and browser tabs to navigate by keeping everything under one roof.

Then, as your newsletter flourishes, you can tap into a universe of plugins, themes, and design patterns with affordable upgrades, whenever the time’s right. That means you can scale smoothly from a free newsletter to one that starts helping you earn, without feeling penned in by a rigid plan or restricted features.

Kickstart your newsletter

Whether you’re thinking of starting up a paid newsletter from scratch or ready to take your existing one up a notch, there’s no better time than now.

Signing up for Newsletter is the quickest route to writing, publishing, and expanding your audience from scratch. And if you’re switching from another platform? No worries, you can bring existing subscribers along for the ride during the setup process.

Amplify an existing site with newsletter features

But you don’t need to start from zero. At WordPress.com, any site can add or become a newsletter. If you’ve been thinking about growing your audience, you’ve got the Subscribe Block and Newsletter Patterns at your disposal to get up and running quickly. They’re the perfect duo to transform a fleeting visit into a lasting bond.

Getting started

Once you’re all set up, introducing paid subscriptions or content gating to your newsletter is simple stuff. Whenever you publish a post, just tick a box to make any post available to everyone, subscribers-only, or just the paying ones.

Here’s how to get started:

Click on “Earn” in the Tools section.

Set up a Stripe account to start receiving payments (or connect your existing account).

Configure your payment plan to establish your subscription fee and cadence.

Your readers will be able to pay for subscriptions directly from your site, with transaction fees as low as 10% of revenue on the Free plan, decreasing as you level up to our paid plans, down to a 0% fee on the Commerce plan. Payments are processed through Stripe and are available in the countries where Stripe is currently supported.

You’re in great company

With over 20 million emails sent out every day by WordPress.com to pretty much every country in the world, rest assured that your newsletter will land in your audience’s inbox reliably and securely. And as your audience grows, you can sit back comfortably knowing that WordPress.com is finely tuned to scale with your ambitions. However far you want to take things.

What’s next?

Newsletter is ever-evolving, and we’re always on the case refining the design, experience, and offerings for writers, creators, and publishers like you. We’re all ears for your ideas for our next steps in making it easier for more people to publish and earn from their work, without barriers to getting started.

Get started today

Quelle: RedHat Stack

2. Juni 2023

da Agency

Docker Desktop 4.20: Docker Engine and CLI Updated to Moby 24.0

We are happy to announce the major release of Moby 24.0 in Docker Desktop 4.20. We have dedicated significant effort to this release, marking a major milestone in the open source Moby project.

This effort began in September of last year when we announced we were extending the integration of the Docker Engine with containerd. Since then, we have continued working on the image store integration and contributing this work to the Moby project.

In this release, we are adding support for image history, pulling images from private repositories, image importing, and support for the classic builder when using the containerd image store.

To explore and test these new features, activate the option Use containerd for pulling and storing images in the Features in Development panel within the Docker Desktop Settings (Figure 1).

Figure 1: Select “Use containerd for pulling and storing images” in the “Features in development” screen.

When enabling this feature, you will notice your existing images are no longer listed, but there’s no need to worry. The containerd image store functions differently from the classic store, and you can only view one of them at a time. Images in the classic store can be accessed again by disabling the feature.

On the other hand, if you want to transfer your existing images to the new containerd store, simply push your images to the Docker Hub using the command docker push <my image name>. Then, activate the containerd store in the Settings and pull the image using docker pull <my image name>.

You can read all bug fixes and enhancements in the Moby release notes.

SBOM and provenance attestations using BuildKit v0.11

BuildKit v0.11 helps you secure your software supply chain by allowing you to add an SBOM (Software Bill of Materials) and provenance attestations in the SLSA format to your container images. This can be done with the container driver as described in the blog post Generating SBOMs for Your Image with BuildKit or by enabling the containerd image store and following the steps in the SBOM attestations documentation.

New Dockerfile inspection features

In version 4.20, you can use the docker build command to preview the configuration of your upcoming build or view a list of available build targets in your Dockerfile. This is particularly beneficial when dealing with multi-stage Dockerfiles or when diving into new projects.

When you run the build command, it processes your Dockerfile, evaluates all environment variables, and determines reachable build stages, but stops before running the build steps. You can use –print=outline to get detailed information on all build arguments, secrets, and SSH forwarding keys, along with their current values. Alternatively, use –print=targets to list all the possible stages that can be built with the –target flag.

We also aim to present textual descriptions for these elements by parsing the comments in your Dockerfile. Currently, you need to define BUILDX_EXPERIMENTAL environment variable to use the –print flag (Figure 2).

Figure 2: Using the new `–print=outline` command outputs detailed information on build arguments, secrets, SSH forwarding keys and associated values.

Check out the Dockerfile 1.5 changelog for more updates, such as loading images from on-disk OCI layout and improved Git source and checksum validation for ADD commands in the labs channel. Read the Highlights from the BuildKit v0.11 Release blog post to learn more.

Docker Compose dry run

In our continued efforts to make Docker Compose better for developer workflows, we’re addressing a long-standing user request. You can now dry run any Compose command by adding a flag (–dry-run). This gives you insight on what exactly Compose will generate or execute so nothing unexpected happens.

We’re also excited to highlight contributions from the community, such as First implementation of viz subcommand #10376 by @BenjaminGuzman, which generates a graph of your stack, with details like networks and ports. Try docker compose alpha viz on your project to check out your own graph.

Conclusion

We love hearing your feedback. Please leave any feedback on our public GitHub roadmap and let us know what else you’d like to see. Check out the Docker Desktop 4.20 release notes for a full breakdown of what’s new in the latest release.

Quelle: https://blog.docker.com/feed/