DEV Community: Nomodo.io

Happy 2025 from Nomodo! 🎉

Nomodo.io — Tue, 31 Dec 2024 00:00:00 +0000

Here at Nomodo.io, we think the new Year is ideal for innovative ideas, bold projects, and simple DevOps. We are celebrating 2025 with Medusa 2.x and brand-new pricing based on used system resources. Our services are even more available and affordable.

Happy coding, and Happy New Year!

Nomodo Pricing Update: $4 Per Seat + Resource Usage

Nomodo.io — Mon, 30 Dec 2024 08:30:07 +0000

This change reflects the feedback we’ve received from you, our users—particularly those who want to quickly spin up solutions with Medusa JS while still having fine‑grained control over monthly expenses. Now entrance in Medusa JS Cloud is more accessible. Just start/stop instance and save money.

What Does This Mean for You?

Previous Model : A fixed price starting at $15/month for your Medusa application.

New Model : A monthly fee starting at $4 per seat per month plus used resource charges (CPU, RAM, HDD).

This approach helps you save money during development and test phases when resource requirements are low, while still giving you the freedom to scale up for production.

The New Pricing Details

Seat pricing:

Hobby : $4/month per seat
Developer : $9/month per seat
Team : $15/month per seat

Resource usage rates:

CPU : $0.015 per core per hour
RAM : $0.0065 per GB per hour
HDD : $0.00035 per GB per hour

Example 1: Development

Developers who are actively working on projects 8 hours per day (160 hours per month) pay only $11.33 per month.

Example 2: Production

Here’s a rough example of running a Medusa instance with 1 CPU, 2 GB of RAM, and 8 GB of HDD 24/7 for one month:

Resource costs (1 CPUs, 2 GB RAM, 8 GB HDD around the clock): approximately $22.92
Seat price (Hobby Plan): $4
Total maximum estimated cost : $26.92

Why the Change?

Pay Only for What You Need : You no longer have to pay for unused resources. If you’re in early development, you’ll only be charged for minimal usage.
Transparent and Predictable : Costs scale with your actual usage. The cost will not break you; autoscaling is disabled by default.
Community‑Driven : We’ve heard your requests—especially from teams and individuals needing to adopt Medusa JS quickly—and have responded with a plan that can adapt as you grow.

Learn more about the new pricing or start your free trial today.

Try Medusa JS with a new pricing, save costs!

Start Medusa.js free trial

Frequently Asked Questions

Billing Cycle : We will invoice monthly based on your actual usage over the prior month. Seats are prorated if you add or remove seats mid‑cycle.
Seat : A seat is any person/account with access to the Nomodo platform. If you collaborate with more developers or contributors, you may need more seats.
Monitoring & Alerts : You’ll be able to set usage alerts and budget caps in your dashboard. No surprise bills!
Ongoing Audits : Our security team regularly reviews and updates our infrastructure to protect your workloads.
Migration: If you’re on an older plan, you can stick with it until it expires or switch to this new, usage‑based model whenever you’re ready. Please note that any new features may only be available on the new plans.
Auto‑scaling is optional. Ask us, and we will enable this feature.

Wrap ‑ up

Nomodo’s new pricing structure—combining a low monthly seat fee with resource‑based billing—offers unprecedented flexibility, making it easier than ever to build and scale Medusa‑based solutions. Whether you’re a solo developer experimenting for a few hours each week or a large team deploying 24/7, you pay only for the actual resources you use. This transparent, community‑driven approach ensures that you remain in full control of costs while still benefiting from robust security and top‑tier support. We invite you to explore the new pricing model, optimise your workloads, and let Nomodo empower your Medusa development journey.

Extend the Holiday Spirit with Medusa JS 2.0 on Nomodo!

Nomodo.io — Fri, 27 Dec 2024 09:15:14 +0000

What’s New in Medusa JS 2.0?

Enhanced Scalability: Effortlessly manage increasing store traffic.
Streamlined GitHub Integration: Sync and deploy your code seamlessly.
Advanced Monitoring Tools: Gain real-time insights into your app's performance.
Customisable Dashboards: Personalise your MedusaJS interface to suit your needs.
Ready-to-Code Setup: Begin building your dream store within minutes.

For a comprehensive list of updates, visit the MedusaJS GitHub Releases page.

Treat Yourself to Hassle-Free Deployment

🎁

Use code NHMSCVBU for a $5 discount.

Get Started with MedusaJS 2.0 Today

New Hosting Plans on Nomodo.io

We’ve listened to your feedback and are excited to announce our switch to a Pay-as-You-Go pricing model! Previously, Nomodo charged a flat fee of $15 per application or $4 per seat plus resource usage. Now, you’ll only pay for the resources you actually use.

👉 Learn more about this exciting update and how it works.

Can We Help More?

MedusaJS is currently at version 2.1.3. How challenging is it for you to upgrade from 2.0.0 to 2.1.3? Share your experience with us on Discord. Let’s work together to make your upgrade process smoother.

Happy holidays and happy coding from all of us at Nomodo.io! 🎄✨

Changelog 2024/48 aka We 🖤 Svelte 5

Nomodo.io — Mon, 25 Nov 2024 23:00:00 +0000

We have rewritten our platform's frontend using Svelte 5, streamlining our workflow and refining our codebase to develop a more flexible and sustainable codebase. The following elements were notable.

What We Appreciate in Svelte 5

Reusable Snippets Replacing Slots
Callbacks Replacing Dispatchers
Simplified Prop Handling with $props
Improved Component Typing
Explicit Reactivity with Runes
Reduced Bundle Sizes

1. Reusable Snippets Replacing Slots

Svelte 5's new snippets system provides a powerful alternative to the slot-based system from Svelte 4. Where we previously used named slots with <svelte:fragment slot="name">, we now leverage the more flexible snippet syntax {#snippet name()}. This allows passing parameters to template fragments and maintaining reactivity, making complex UI patterns like recursive components and compound components more straightforward. Our modal and dropdown components benefit from this change, as content can be dynamically injected while preserving state and context.

<!-- Parent.svelte -->
<Card>
  <svelte:fragment slot="title">
    My Card Title
  </svelte:fragment>
  <svelte:fragment slot="content">
    Card content here
  </svelte:fragment>
</Card>

<!-- Card.svelte -->
<div class="card">
  <div class="title">
    <slot name="title" />
  </div>
  <div class="content">
    <slot name="content" />
  </div>
</div>

Svelte 4

<!-- Parent.svelte -->
<Card>
  {#snippet title()}
    My Card Title
  {/snippet}

  {#snippet content()}
    Card content here
  {/snippet}
</Card>

<!-- Card.svelte -->
<script>
  let { title, content } = $props();
</script>

<div class="card">
  <div class="title">
    {@render title()}
  </div>
  <div class="content">
    {@render content()}
  </div>
</div>

Svelte 5

2. Callbacks Replacing Dispatchers

Component communication is more straightforward with Svelte 5's approach to props and callbacks compared to event dispatchers. Where Svelte 4 required using createEventDispatcher pattern with dispatch('submit', { data }) and handling it with on:submit event listeners, Svelte 5 enables passing callback functions directly through props <Child onSubmit={handleSubmission} />. This reduces boilerplate, provides better TypeScript integration, and makes data flow more explicit throughout the application.

<!-- Child.svelte -->
<script>
  import { createEventDispatcher } from 'svelte';
  const dispatch = createEventDispatcher();

  function handleSubmit(data) {
    dispatch('submit', { data });
  }
</script>

<!-- Parent.svelte -->
<Child on:submit={({ detail }) => handleSubmission(detail.data)} />

Svelte 4

<!-- Child.svelte -->
<script>
  let { onSubmit } = $props();

  function handleSubmit(data) {
    onSubmit?.(data);
  }
</script>

<!-- Parent.svelte -->
<Child onSubmit={handleSubmission} />

Svelte 5

3. Simplified Prop Handling with $props

Svelte 5's $props rune brings a cleaner approach to component properties. The verbose export let syntax from Svelte 4 is replaced with a single destructuring statement let { prop1 = defaultValue, prop2 } = $props(). This approach significantly reduces code verbosity, improves TypeScript integration, significantly reduces prop-related boilerplate in components, and strengthens type checking.

4. Improved Component Typing

The typing improvements in Svelte 5 have been another standout feature for us. Built-in typed properties like placeholder and maxlength now function seamlessly, while custom traits can be defined with precision to ensure type safety. These enhancements have not only reduced the risk of runtime errors but have also made our code more robust and maintainable. Additionally, the deeper integration with TypeScript has significantly improved productivity and reliability.

5. Explicit Reactivity with Runes

Svelte 5's runes system represents a fundamental shift in reactivity management. Instead of Svelte 4's implicit reactivity with let declarations and $: statements, Svelte 5 uses explicit runes like $state() and $derived(). A typical example shows this evolution:

// Svelte 4
let count = 0;
$: tripled = count * 3;

// Svelte 5
let count = $state(0);
let tripled = $derived(count * 3);

6. Reduced Bundle Sizes

The new compiler in Svelte 5 has brought significant optimisations, leading to bundle size reductions of up to 50% compared to Svelte 4. This efficiency boost not only improves performance but also aligns with our commitment to delivering a lightweight and fast platform.

A Worthwhile?

While adopting Svelte 5 and its new features—like snippets, callbacks, and runes—required some adjustments to our workflow, the results have been well worth the effort. The new features we’ve integrated have allowed us to create a cleaner, more scalable codebase. These changes are already helping us work more efficiently and will undoubtedly lead to fewer bugs and a smoother development experience in the long term.

To stay updated on what’s new at Nomodo, follow us on Twitter or join our Nomodo.io Discord channel. Also, don’t miss exploring MedusaJS.

From all of us at Nomodo.io, thank you for being part of our journey!

Announcing Deployment and Build Logs

Nomodo.io — Mon, 18 Nov 2024 14:45:45 +0000

Why you’ll love it:

Clear Deployment Progress: See each step of your deployment as it happens, from setup to app launch.
Detailed Build Insights: Easily identify and resolve issues with full build logs, showing every dependency installation and environment configuration.

How It Works

Head to the Deploys tab in your app.
Select the deployment you want and open the details page.
Scroll down to view Deployment Logs and Build Logs in real time.

Whether you’re tracking progress or solving a problem, all the data you need is now at your fingertips.

Ready to Give It a Go?

Log in to admin.nomodo.io and try it out today. Got feedback? We’d love to hear from you—drop us a line or join the chat on our community page.

Deploy smarter, not harder! 🚀

Getting Started with Your Medusa.js on Nomodo

Nomodo.io — Mon, 28 Oct 2024 14:00:22 +0000

By using Medusa.js on Nomodo, you get a powerful backend platform enriched with several Nomodo-specific features, such as automatic backups, easy deployment options, monitoring tools, and IP whitelisting to ensure your store runs smoothly and securely. For full functionality, you will need a file storage plugin to display product thumbnails effectively. We recommend using the S3 bucket plugin, either through our Nomodo solution or your personal AWS account, for optimal performance and accessibility.

1. Dive into Your Medusa.js Admin Dashboard

The Admin Dashboard is where you’ll manage every aspect of your application—products, orders, inventory, and more. Once you log in, you can start setting up products, adjusting inventory levels, and configuring various order settings.

Get Started Tips:

Familiarise yourself with the layout.
Set up a few test products.
Play around with managing orders to get comfortable with the system.

You can find more information on using the Medusa admin dashboard in the official intro.

2. Customise Medusa.js Locally

To take full control, it’s time to dive into some customisation. Here’s how to get started locally:

Clone the repository to your local environment.
Make the changes you want—adjust the design, add functionalities, or remove anything you don’t need.
Push your changes back to your repository.

3. Deploy Your Updates

Ready to make your improvements live? Deploying changes ensures that everything you work on locally is reflected in your live version.

To deploy:

Go to the Deploys tab in Dashboard.
Click on New Deployment.
Sit back and relax while your changes go live!

4. Add Cloud Storage with S3 Bucket

Managing images, especially when dealing with product photos or other media, requires reliable cloud storage. You can also explore more options for file storage in the official list of file plugins.

Additionally, check out our article on How to Configure MinIO Plugin for File Storage in MedusaJS Locally, which is a great option if you do not have or do not want to use an AWS account. MinIO allows you to store files in a bucket similar to Amazon S3 but in your own local environment.

We also have a guide for Setting up and connecting AWS S3 to the MedusaJS backend, covering implementation of the required plugins.

5. Launch Your Storefront

Want to showcase your products? We offer the standard storefront using The official Next.js DTC Starter by Medusa, which we can install for you on demand if you do not already have your own frontend solution. The storefront must remain standalone, allowing multiple frontends to connect to the same Medusa backend. These frontends can be written with different frameworks, run on different URLs, and serve different needs. Learn more about available starters in the Medusa documentation.

Have your own storefront on the Vercel? Read this article on How to Set Up MedusaJS Backend with a Storefront on Vercel.

6. Automatic Backups for Data Safety

Your data is automatically backed up every hour, without any action needed from you. These backups are particularly useful when making changes to the database structure or during data manipulation, ensuring you can always recover your information if needed.

7. Manage Database Access with IP Whitelisting

IP whitelisting is a default security feature on Nomodo.io, ensuring only authorized IP addresses can access your data. This adds an essential layer of protection, especially for environments handling sensitive information. For more details, check out our article on IP Whitelisting: Default Security on Nomodo.io

8. Monitor System Performance

Good performance is key to keeping customers happy. You can monitor your system’s CPU, memory, and disk usage directly from the admin interface to keep an eye out for potential issues before they arise.

9. Debugging with Logs

Logs are an essential tool for tracking down issues and ensuring everything is running as it should. Whether you're a developer or just looking to understand your store better, application and system logs provide insights to fine-tune your setup.

IP Whitelisting: Default Security on Nomodo.io

Nomodo.io — Thu, 24 Oct 2024 06:00:00 +0000

When Will You Need to Whitelist an IP?

If you're running a local instance (like from localhost) or need to connect external apps or services, you’ll need to manually add their IP addresses to the whitelist.

How to Whitelist an IP on Nomodo.io

Go to Database > Access Management in your app detail.
Choose “TCP” in the Protocol select.
Put the IP string into “CIDR address”. A tool like ipinfo.io helps find your IP or the public IP of the app/service.
Add /0 to allow access from a wide range of IPs, or use /32 to restrict access to a single IP address.
In the “Port” input, paste the value from “DB Port” in the tab Database > Database Info.

Why Does This Matter?

Whitelisting ensures that only trusted sources can connect to your database—keeping unwanted access at bay. So, every time you work in a new environment or add new services, don’t forget to update your whitelist.

Note: IP addresses may change over time, so ensure your current address is always updated. If you cannot connect, check if your IP is still listed.

Heroku vs. Nomodo: A Comprehensive Comparison

Nomodo.io — Tue, 22 Oct 2024 10:00:00 +0000

Overview

Heroku is a popular cloud Platform as a Service (PaaS) known for simplifying app deployment with its container-based "Dynos." It supports multiple programming languages like Node.js and Ruby. While effective, it requires technical expertise, which Nomodo simplifies with its developer-first approach.

Heroku

Heroku simplifies infrastructure management, offering deployment services, automatic scaling, and database options like Heroku Postgres and Redis. However, developers must manually configure and maintain Dynos, as well as integrate additional services to meet project requirements. While suitable for many teams, this approach demands technical expertise and ongoing oversight.

Nomodo

Nomodo focuses on a developer-first approach, providing pre-configured open-source applications as a service. With Nomodo, developers can deploy apps without delving into the intricacies of infrastructure, containerisation, or scaling. The platform manages setup, scaling, and maintenance, allowing teams to focus solely on their projects. Whether it’s Medusa, Grav, PostgreSQL, or other applications, Nomodo handles the heavy lifting.

Comparison of Features

Feature	Heroku	Nomodo
Type of Service	PaaS	Open-source apps as a service
Supported Tech	Node.js, PHP, Ruby, Python	Varies by app
Container System	Dynos	—
Database Support	Heroku Postgres, Redis, etc.	PostgreSQL, Redis, Kafka, MySQL, etc.
Scaling	Automatic, with manual setup	Fully automatic, no configuration
Add-ons	Extensive but manual setup	Pre-installed, tailored plugins
Audience	Developers, Enterprises	Developers, open-source teams
DevOps Complexity	Requires knowledge	Minimal to none

Addressing Developer Challenges

Common Issues with Heroku:

Complex Installation & Setup: Time-intensive and requires expertise.
Server maintenance burden: consumes resources and developer focus.
DevOps Overhead: Scaling and monitoring add complexity.
Vendor Lock-In: Limited options for scalability beyond Heroku's ecosystem.

How Nomodo Solves These:

One-Click Deployments: Deploy in seconds without technical know-how.
Managed Infrastructure: No server management is needed.
Automated DevOps: Fully automated scaling, updates, and backups.
Multi-Cloud Flexibility: Avoid vendor lock-in by choosing your cloud provider.

Conclusion

While Heroku remains a robust choice for many developers, Nomodo redefines app deployment for those seeking simplicity, flexibility, and time savings. Whether you're a seasoned developer or new to app hosting, Nomodo empowers you to focus on building exceptional products rather than managing infrastructure.

Start exploring how Nomodo can elevate your development experience today!

How to Configure MinIO Plugin for File Storage in MedusaJS Locally

Nomodo.io — Fri, 18 Oct 2024 06:30:13 +0000

Prerequisites

Knowledge of environment variables
Installed MedusaJS project
Access to Nomodo.io for receiving MinIO credentials

TL;DR

Set up environment variables.
Install the MinIO plugin via npm.
Add the plugin to your Medusa config file.
Test the configuration locally.

Step 1: Set Up Environment Variables

To connect your local Medusa project to MinIO for file storage, you'll need certain environment variables. These are provided by Nomodo.io when you set up your instance. Here's an example of what the environment variables might look like:

MINIO_ENDPOINT="https://s3.nomodo.io/your-instance-id"
MINIO_BUCKET="your-instance-id"
MINIO_ACCESS_KEY="your-access-key"
MINIO_SECRET_KEY="your-secret-key"

Note: You will receive the actual values for these variables from Nomodo. Do not use the placeholders above.

Add these values to your local .env file. This will allow Medusa to use them during local development.

Example .env file:

MINIO_ENDPOINT="https://s3.nomodo.io/medcs0elg85iop2o82rj3n0"
MINIO_BUCKET="medcs0elg85iop2o82rj3n0"
MINIO_ACCESS_KEY="Your_Access_Key_Here"
MINIO_SECRET_KEY="Your_Secret_Key_Here"

Step 2: Install the MinIO Plugin

Next, you'll need to install the medusa-file-minio plugin, which adds support for MinIO as a file storage solution for your Medusa backend.

Use npm to install the plugin by running:

npm install medusa-file-minio

This plugin enables your Medusa backend to seamlessly upload and store files on your MinIO instance. For further information and advanced configuration options, check out the official medusa-file-minio plugin documentation.

Step 3: Add MinIO Plugin to Your Medusa Configuration

Once the plugin is installed, you’ll need to configure it by adding it to your Medusa config file. Open your Medusa configuration file (medusa-config.js or medusa-config.ts), and include the following code:

{
  resolve: 'medusa-file-minio',
  options: {
    endpoint: process.env.MINIO_ENDPOINT,
    bucket: process.env.MINIO_BUCKET,
    access_key_id: process.env.MINIO_ACCESS_KEY,
    secret_access_key: process.env.MINIO_SECRET_KEY,
  },
},

This configuration allows Medusa to use the MinIO plugin for file storage, leveraging the environment variables you defined earlier.

Step 4: Test the Local Setup

After configuring the plugin, it’s time to test if everything is working correctly. Start your local Medusa server:

npm run dev

Now, try uploading a file through the Medusa admin panel or your store’s frontend. If everything is configured properly, the file should be successfully uploaded to your MinIO bucket.

Troubleshooting : If the file upload fails, ensure that the environment variables are correctly set and check the logs for errors. Also, verify that your access keys and secrets are valid.

Deploy—put it live

Once your changes are ready, commit and push them to the remote repository:

git add .
git commit -m "Your message"
git push origin master

Copy these ENV variables into Settings > Environment Variables app detail. After you’ve filled in all the variables, press the “Reload” button, which will run a new deployment in the background. Until the deployment is complete, the Medusa.js backend will not be available, but don’t worry, it will only take a few seconds.

Conclusion

Setting up file storage for your MedusaJS store using the MinIO plugin locally is a straightforward process. With the environment variables provided by Nomodo.io and a quick plugin installation, you’ll be ready to handle file uploads seamlessly.

This setup allows you to offload file management to MinIO’s robust storage infrastructure while keeping your Medusa backend clean and efficient. Try it out, and if you need more help, don’t hesitate to reach out to the Nomodo support team!

Try Medusa.js

Use code B0OZUUYW for a discount. We 💙 our readers.

Start Medusa.js free trial

How to Develop MedusaJS Locally and Deploy Live

Nomodo.io — Fri, 18 Oct 2024 05:30:47 +0000

Prerequisites

Knowledge of Git and environment variables
Access to a Nomodo.io account

TL;DR

Clone the MedusaJS repository
Install dependencies and build packages
Optionally link with the live instance on Nomodo
Commit, push changes, and deploy your app live

Step 1: Clone the MedusaJS Repository

Go to Settings > Git Integration in your Nomodo dashboard. If you see nomodoapp/ at the start of the repository name, you previously chose deployment without GitHub integration—ask support for access.

# Clone repository
git clone https://github.com/cebreus/MyAwesome_medcs6bn6g5iopbvf9mdo80.git

# Go to project repository
cd MyAwesomeMedusa_medcs6bn6g5iopbvf9mdo80

Example Tip: Ensure you have the correct permissions to access the repository.

Step 2: Install Dependencies and Build Packages

Install the required dependencies to run MedusaJS.

npm install

Install dependencies, e.g. with the pnpm

Tip: For more information on configuring local development, check out the official documentation.

Step 3: Optionally Link with a Live Instance on Nomodo

To connect your local project to a live instance, go to Settings > Environment Variables in Nomodo and copy the variables into your local .env file. The Source of truth of the DB connection string is in the tab Database > Database Info.

DATABASE_URL="postgres://postgres:s3f6syra58jphm492a07ii@3.121.231.62:5432/medcs6bn6g5iopbvf9mdo80"
REDIS_URL="redis://:m5pnv313yq7fbgeuquhl91&3.121.231.62:6379"

Example of .env file

Access Management

For security reasons, Nomodo.io blocks external requests to the database. You must add your current IP address (in CIDR format) under Database > Access Management.

Choose “TCP” in the Protocol select
Find your actual IP address (e.g., via ipinfo.io).
Add /0 to allow access from a wide range of IPs, or use /32 to restrict access to a single IP address.
Put this string into “CIDR address”
In the “Port” input paste value from “DB Port” in the tab Database > Database Info.

Note: IP addresses may change over time, so ensure your current address is always updated. If you cannot connect, check if your IP is still listed.

Step 4: Run, Push, Deploy

Run your code locally using:

npm run dev

Once your changes are ready, commit and push them to the remote repository:

git add .
git commit -m "Your message"
git push origin master

From the Nomodo dashboard, go to Deploys and click on New Deployment.

If errors occur (such as environment variable issues), update them in Settings > Environment Variables. You may also need to run migration scripts if your changes involve modifying the database structure. Go to Database > Migrations to handle this.

If things go wrong, you can roll back to a previous working state from the deployment history.

Conclusion

Developing and deploying MedusaJS on Nomodo.io is a straightforward process, made easier with features like automatic database backups , easy environment management , and the ability to roll back deployments if needed. Whether you’re pushing small updates or significant changes requiring migrations, Nomodo.io simplifies the entire process, allowing you to focus on building your e-commerce solution without worrying about infrastructure.

Happy coding!

Try Medusa.js

Use code B0OZUUYW for a discount. We 💙 our readers.

Start Medusa.js free trial

26 Global Regions for MedusaJS Hosting on Nomodo.io!

Nomodo.io — Wed, 28 Aug 2024 13:00:53 +0000

Global connectivity with MedusaJS as we introduce 25 new hosting regions across the globe. Now, your e-commerce platform can deliver top-tier performance, no matter where your customers are. Discover how this expansion empowers your business with faster, more reliable, and compliant operations.

What’s New?

Nomodo.io now supports hosting your MedusaJS backend in the following regions:

North America :
- US East : N. Virginia, Ohio
- US West : N. California, Oregon, Canada (Central and Calgery)
South America : São Paulo
Europe : Frankfurt, Ireland, London, Milan, Paris, Stockholm, Spain
Africa : Cape Town
Asia Pacific : Hong Kong, Mumbai, Osaka-Local, Seoul, Singapore, Sydney, Tokyo, Jakarta, Melbourne, Malaysia, Hyderabad

Why This Matters

With the addition of these regions, you can now deploy your MedusaJS backend closer to your customer base, minimising latency and ensuring faster load times. This is especially crucial for businesses operating globally, where performance and reliability are key to customer satisfaction.

Affordable, Scalable Solutions

Our hosting plans are designed to be flexible and scalable, catering to startups and growing businesses alike. Prices range from $10 to $30 per month, depending on your specific needs. Plus, with our 7-day free trial , you can experience the power of MedusaJS on Nomodo.io without any upfront commitment.

Ready to Get Started?

Deploying your MedusaJS backend in these new regions is as easy as a few clicks. Whether you’re a developer or a business owner, Nomodo.io simplifies the process, allowing you to focus on what matters most—building and scaling your business.

Try it out today and take advantage of our global network to deliver the best possible experience to your users!

Try Medusa.js

Use code MedusaJSYT5 for a $5 discount.

Start Medusa.js free trial

How to setup Stripe plugin in Medusa.js on Nomodo: Step‑by‑Step Guide

Nomodo.io — Wed, 28 Aug 2024 06:00:37 +0000

Prerequisites:

MedusaJS instance on nomodo.io
Stripe account
Front-end MedusaJS store.

This guide has three steps:

Install and configure the Stripe plugin.
Change environment variables and deploy via Nomodo admin
Configuring stripe environment variables according to the Stripe documentation and restarting the application

1. Install and configure the Stripe plugin.

To begin, we expect that you have an already running medusajs project on Nomodo, and a running medusajs project on your local machine.

Let’s continue by installing the stripe plugin, run the command below:

npm i medusa-payment-stripe@^6.0.10

If the installation is successful, the stripe plugin will be added to your package.json file.

To configure the plugin, open the medusa-config.js file and add the following at the end of the plugins array:

const plugins = [
 // ....
 {
   resolve: `medusa-payment-stripe`,
   options: {
     api_key: process.env.STRIPE_API_KEY,
     webhook_secret: process.env.STRIPE_WEBHOOK_SECRET,
   },
 },
];

1.1 Get and store Stripe API keys

The plugin accepts an api_key , necessary for both your development and production environments, and webhook_secret required for your production environment.

To get your api_key go to your Stripe’s account dashboard and create a new account for your MedusaJS project:

Once your account is created, click on the developers tab, then API keys section under it.

Click to reveal your secret key:

Click to copy the key, add to your medusa backend .env.local file in your local machine.

Once done, restart your medusa js locally with npm run start , and open the Medusa admin on localhost:7001

1.2. Updating Environment Variables in Nomodo.io admin

These Stripe’s environment variables, the secret_key and the webhook_secret must also be saved in the nomodo.io admin; go to Settings → Environmental variables and add accordingly. Once done, you can click on Restart or Redeploy to propagate the changes.

1.3 Adding Regions in Medusa.js

In this section, we will learn how to manage stripe payments as per region, this enables a customer to select Stripe as a payment provider during checkout to complete their purchases.

Go to the Settings section on the sidebar and select Regions :

Click on the + icon to add a new region

You will be required to add region details, including currency, taxes, payment, and fulfilment providers.

On the Payment Providers dropdown list, select Stripe , and on the Fulfilment Providers dropdown list select the Manual option. Save and close.

To view the region details created, click on Region’s top right hand, then click Edit Region Details button.

At this point, everything in the MedusaJS backend is now configured.

1.4 Adding Stripe in Frontend

If you have no frontend repository, a quick setup guide is provided here, use the 2nd option as you already have a running medusa backend, follow the instructions to create a Next.js storefront separately.

For the stripe payment to work on the front-end, you need to get stripe’s “ publishable key ” from the developers tab under api keys in your stripe account dashboard:

Add the key in the .env.local file in your front-end code, this will help in testing the stripe payment method from the UI, and restart the frontend server.

1.5. Test Stripe integration on frontend

To test stripe payment method, go to the store catalogue, in this case http://localhost:8000/us/store, this displays a list of items in “ us” store, “ us ” being the default region set in our .env.local file with the NEXT_PUBLIC_DEFAULT_REGION key, select an item and add to cart.

Navigate to Cart to checkout the items.

To checkout, click Go to checkout , add your shipping address, delivery method and click Continue to payment.

An option to add credit card details is now shown, we will use Stripe’s test card number.

Once payment is added, click Continue to review , and finally Place the order to complete the checkout process.

2. Deploy the new version via Nomodo admin.

Push your local changes to your GitHub remote repository.
Open the applications’s Nomodo admin instance, go to Settings → Environmental variables and add the Stripe’s Environment variables.
Click on the Restart button to propagate the changes.
If you want to deploy and make all changes available, perform a deploy (App Details, Deployments tab).

3. Configure Stripe’s Environment variables and restart the application.

Stripe provides two main environments, development and production environments, which each require different setups. A complete guide is provided in the Stripe’s official documentation.

3.1 Testing Environment

For the development environment, Stripe provides an api_key , that will help you simulate real-world transactions, with a variety of test card numbers to test for various payment scenarios, like successful payments, failed payments and refunds.

It also provides webhook_secret, this hook can be pointed to your MedusaJS backend local server {BACKEND_URL}/stripe/hooks and set to listen to selected events Stripe sends after a transaction is completed.

3.2 Production Environment

In production environment, Stripe provides live API keys which handle real transactions, it also provides webhook_secret, the webhook_secret is now configured to point to your production server. The webhook handles real events related to payments, disputes, refunds, etc.

3.3 Deployment to Nomodo.io

Deployment to any stripe environment, is just a few clicks using the nomodo.io admin. Go to Settings → Environmental variables and update Stripe’s environment variables. Once done, you can click on Restart or Redeploy to propagate the changes.

Overview

You’ve now successfully set up stripe plugin as a payment method for your MedusaJS project, and deploying it to Nomodo is just few clicks. Thanks to Nomodo, you can stop worrying about your business revenue management cycle and instead focus on creating amazing experiences for your customers. Give Nomodo a try and experience seamless deployment today!

Try this integration with Medusa.js free trial

Use code MedusaJSYT5 for a $5 discount.

Start Medusa.js free trial

DEV Community: Nomodo.io

Happy 2025 from Nomodo! 🎉

Here at Nomodo.io, we think the new Year is ideal for innovative ideas, bold projects, and simple DevOps. We are celebrating 2025 with Medusa 2.x and brand-new pricing based on used system resources. Our services are even more available and affordable.

Nomodo Pricing Update: $4 Per Seat + Resource Usage

What Does This Mean for You?

The New Pricing Details

Example 1: Development

Example 2: Production

Why the Change?

Try Medusa JS with a new pricing, save costs!

Frequently Asked Questions

Wrap ‑ up

Extend the Holiday Spirit with Medusa JS 2.0 on Nomodo!

What’s New in Medusa JS 2.0?

Treat Yourself to Hassle-Free Deployment

New Hosting Plans on Nomodo.io

Can We Help More?

Changelog 2024/48 aka We 🖤 Svelte 5

What We Appreciate in Svelte 5

1. Reusable Snippets Replacing Slots

2. Callbacks Replacing Dispatchers

3. Simplified Prop Handling with $props

4. Improved Component Typing

5. Explicit Reactivity with Runes

6. Reduced Bundle Sizes

A Worthwhile?

Announcing Deployment and Build Logs

How It Works

Ready to Give It a Go?

Getting Started with Your Medusa.js on Nomodo

1. Dive into Your Medusa.js Admin Dashboard

2. Customise Medusa.js Locally

3. Deploy Your Updates

4. Add Cloud Storage with S3 Bucket

5. Launch Your Storefront

6. Automatic Backups for Data Safety

7. Manage Database Access with IP Whitelisting

8. Monitor System Performance

9. Debugging with Logs

We’re Here to Help

IP Whitelisting: Default Security on Nomodo.io

When Will You Need to Whitelist an IP?

How to Whitelist an IP on Nomodo.io

Why Does This Matter?

Heroku vs. Nomodo: A Comprehensive Comparison

Overview

Heroku

Nomodo

Comparison of Features

Addressing Developer Challenges

Common Issues with Heroku:

How Nomodo Solves These:

Conclusion

How to Configure MinIO Plugin for File Storage in MedusaJS Locally

Step 1: Set Up Environment Variables

Step 2: Install the MinIO Plugin

Step 3: Add MinIO Plugin to Your Medusa Configuration

Step 4: Test the Local Setup

Deploy—put it live

Conclusion

Try Medusa.js

How to Develop MedusaJS Locally and Deploy Live

Step 1: Clone the MedusaJS Repository

Step 2: Install Dependencies and Build Packages

Step 3: Optionally Link with a Live Instance on Nomodo

Access Management

Step 4: Run, Push, Deploy

Conclusion

Try Medusa.js

26 Global Regions for MedusaJS Hosting on Nomodo.io!

What’s New?

Why This Matters

Affordable, Scalable Solutions

Ready to Get Started?

Try Medusa.js

How to setup Stripe plugin in Medusa.js on Nomodo: Step‑by‑Step Guide

1. Install and configure the Stripe plugin.

1.1 Get and store Stripe API keys

1.2. Updating Environment Variables in Nomodo.io admin

1.3 Adding Regions in Medusa.js