Forem: Chris

How to Fully Integrate CoppeliaSim in Ubuntu (Command Line & Desktop)

Chris — Tue, 11 Nov 2025 04:31:21 +0000

This guide provides a complete workflow for integrating a manually downloaded CoppeliaSim package into your Ubuntu system.

It covers moving it to a system-wide directory, making it runnable from the terminal, and adding a proper application launcher to your dock (taskbar).

We will assume you have already downloaded and extracted the CoppeliaSim folder, for example, to

~/Downloads/CoppeliaSim_Edu_V4_x_x_Ubuntu...

Part 1: Move CoppeliaSim to a System-wide Location

Using a standard location like /usr/local keeps your home directory clean and is a common practice for manually installed software.

Move the Folder

Open a terminal and move the extracted folder to /usr/local/CoppeliaSim. You will need sudo permissions.

   # Adjust the source path to match your downloaded folder name
   sudo mv ~/Downloads/CoppeliaSim_Edu_V4_x_x_Ubuntu... /usr/local/CoppeliaSim

Adjust Ownership

Change the ownership of the folder to your user. This allows you to run it without sudo and makes it easier to manage.

bash # Replace $USER with your username (or just use the $USER variable) sudo chown -R $USER:$USER /usr/local/CoppeliaSim

Part 2: Set Up Command-Line Access

This allows you to type coppeliasim in your terminal to launch the application from any directory.

Create a Symbolic Link

Link the executable script to a location in your system's PATH.

bash sudo ln -s /usr/local/CoppeliaSim/coppeliaSim.sh /usr/local/bin/coppeliasim

You can now test this by typing:

bash coppeliasim

(Optional) Set Environment Variable

Some integrations (like ROS or Python APIs) expect a COPPELIASIM_ROOT environment variable.
Add this to your shell configuration file (e.g., ~/.bashrc or ~/.zshrc).

bash echo 'export COPPELIASIM_ROOT=/usr/local/CoppeliaSim' >> ~/.bashrc # Apply the changes to your current terminal session source ~/.bashrc

Part 3: Create a Desktop Launcher (Dock Icon)

This creates a clickable icon in your Show Applications menu, which you can then pin to your dock.

Step 3.1: Download and Place a Logo

The default .desktop file may not have a high-quality icon. We can download one and place it in the installation directory.

Download the Logo

bash wget -O ~/Downloads/logo.png https://user-images.githubusercontent.com/8070210/114549467-5793d900-9c61-11eb-88f2-24996a6c03e6.png

Create the Icon Folder

We'll place the logo inside the helpFiles directory. The -p flag creates parent directories if needed.

bash sudo mkdir -p /usr/local/CoppeliaSim/helpFiles

Move and Secure the Logo

bash sudo mv ~/Downloads/logo.png /usr/local/CoppeliaSim/helpFiles/logo.png sudo chown $USER:$USER /usr/local/CoppeliaSim/helpFiles/logo.png sudo chmod 644 /usr/local/CoppeliaSim/helpFiles/logo.png

Step 3.2: Create the `.desktop` File

Application launchers are defined by .desktop files. We will create one for the current user.

bash nano ~/.local/share/applications/CoppeliaSim.desktop

Step 3.3: Edit the `.desktop` File Content

Paste the following into the editor:

ini [Desktop Entry] Name=CoppeliaSim Comment=Robotics simulation software Exec=/usr/local/CoppeliaSim/coppeliaSim.sh Icon=/usr/local/CoppeliaSim/helpFiles/logo.png Terminal=false Type=Application Categories=Science;Education;Robotics; StartupWMClass=CoppeliaSim

Field Explanations

Name: The name that appears in the applications menu.
Exec: The absolute path to the launch script.
Icon: The absolute path to the icon file we just moved.
Terminal: false because this is a GUI application.
Categories: Helps the app show up in the correct menu categories.
StartupWMClass: Ensures the dock recognizes the app window correctly (prevents duplicate icons).

Save and exit nano:

text Ctrl + O, Enter, Ctrl + X

Step 3.4: Find the Correct `StartupWMClass` (Optional but Recommended)

The value CoppeliaSim is often correct, but this can vary.
If you get a duplicate icon on your dock, follow these steps:

Launch CoppeliaSim:

bash coppeliasim

In another terminal, run:

bash xprop | grep WM_CLASS

Click on the running CoppeliaSim window.
The terminal will output something like:

WM_CLASS(STRING) = "some-string", "CoppeliaSim"

The second value (e.g., "CoppeliaSim") is what you should use for StartupWMClass in your .desktop file.

Step 3.5: Make Executable and Add to Dock

(Optional) Make Executable

Some systems require the .desktop file to be executable.

bash chmod +x ~/.local/share/applications/CoppeliaSim.desktop

Add to Favorites (Pin to Dock)

Open the Show Applications menu (the grid icon).
Search for CoppeliaSim.
Right-click it and select Add to Favorites.

You’re all set!
CoppeliaSim is now fully integrated into your Ubuntu system.

Managing Alembic Migrations Across Multiple Environments

Chris — Sat, 14 Jun 2025 10:54:42 +0000

Alembic is a powerful tool for handling SQLAlchemy schema migrations. In real-world projects, you often need to manage separate databases for local, staging, and production environments — each with their own migration history and configuration.

📁 Why Separate Environments?

Local: For development and testing on your machine.
Staging: For testing production-like deployments.
Production: The live environment serving real users.

🔧 Step 1: Extend `alembic.ini`

Update your alembic.ini file to define multiple environments:

[DEFAULT]
prepend_sys_path = .
version_path_separator = os

[alembic]
script_location = alembic/local
sqlalchemy.url = driver://user:pass@localhost/localdb

[staging]
script_location = alembic/staging
sqlalchemy.url = driver://user:pass@staging-server/stagingdb

[production]
script_location = alembic/production
sqlalchemy.url = driver://user:pass@prod-server/proddb

📂 Step 2: Initialize Alembic Environments

Run the following commands to create migration folders for each environment:

`bash

Local environment

alembic init alembic/local

Staging environment

alembic -n staging init alembic/staging

Production environment

alembic -n production init alembic/production
`

This creates a separate env.py and versions/ directory for each environment.

📝 Step 3: Create Migrations

Autogenerate or write new migration scripts for a specific environment:

`bash

Local development

alembic revision --autogenerate -m "add users table"

Staging

alembic -n staging revision --autogenerate -m "add users table"

Production

alembic -n production revision --autogenerate -m "add users table"
`

⬆️ Step 4: Apply Migrations

Apply your changes to the appropriate database:

`bash

Local

alembic upgrade head

Staging

alembic -n staging upgrade head

Production

alembic -n production upgrade head
`

🔍 Step 5: Check Current Revision

`bash

Local

alembic current

Staging

alembic -n staging current

Production

alembic -n production current
`

💡 Note
Ensure that each environment's env.py loads the correct SQLAlchemy metadata (i.e. your models) to detect changes.

📌 Folder Structure

alembic/ ├── local/ │ ├── env.py │ └── versions/ ├── staging/ │ ├── env.py │ └── versions/ └── production/ ├── env.py └── versions/

✅ Summary

Use the -n flag to isolate environments.
Keep migrations separate to avoid cross-environment issues.
Always test in local and staging before applying to production.

Forem: Chris

How to Fully Integrate CoppeliaSim in Ubuntu (Command Line & Desktop)

Part 1: Move CoppeliaSim to a System-wide Location

Part 2: Set Up Command-Line Access

Part 3: Create a Desktop Launcher (Dock Icon)

Step 3.1: Download and Place a Logo

Step 3.2: Create the .desktop File

Step 3.3: Edit the .desktop File Content

Field Explanations

Step 3.4: Find the Correct StartupWMClass (Optional but Recommended)

Step 3.5: Make Executable and Add to Dock

Managing Alembic Migrations Across Multiple Environments

📁 Why Separate Environments?

🔧 Step 1: Extend alembic.ini

📂 Step 2: Initialize Alembic Environments

Local environment

Staging environment

Production environment

📝 Step 3: Create Migrations

Local development

Staging

Production

⬆️ Step 4: Apply Migrations

Local

Staging

Production

🔍 Step 5: Check Current Revision

Local

Staging

Production

📌 Folder Structure

✅ Summary

Step 3.2: Create the `.desktop` File

Step 3.3: Edit the `.desktop` File Content

Step 3.4: Find the Correct `StartupWMClass` (Optional but Recommended)

🔧 Step 1: Extend `alembic.ini`