My name is Ogundele Alimat. I'm excited to be in the community, I’m a professional resume writer, and I help job seekers create ATS-compliant resumes and revamp their existing CVs. If you need help improving your resume or positioning yourself better for job opportunities, feel free to reach out here or send your resume to: ogundelealimat99@gmail.com

For years, I've wanted a straightforward way to create and manage virtual machines. I tried VirtualBox, QEMU/KVM, and a few others, but none felt right for the long haul. My final hope? Proxmox. A few years back, I snagged a cheap used Lenovo ThinkPad. I added a 1TB SSD (I already had two smaller ones), plus 32GB of RAM. Suddenly, I had everything I needed. Preparing the USB stick was a breeze with this command: caligula burn <iso_name> I installed Proxmox, and I have to say, my first impressions are fantastic. I spun up an Ubuntu Server VM in no time, and the simplicity blew me away. Now, I'm excited to experiment more: setting up a backup server, DNS, build pipelines, and whatever else catches my eye. Stay tuned as I dive deeper!

Hello engineers, I was annoyed that I needed to run two separate commands to start the whole app. So, I did some research, asked an LLM, and found a great solution! :) Instead of running the Supabase backend via the CLI, I updated the main Docker Compose file to include all Supabase containers directly. Now, I can just run npm start in the root directory, and the entire project, frontend and backend. Everythink starts at the same time. What I did: - Completely restructured the server directory (following this documentation and this repository) - Ensured all volumes for the backend containers are stored in the server directory. Services I added: - studio - kong - auth - rest - realtime - storage - imgproxy - meta - functions - analytics - db - supavisor Volumes I added: - db-config - deno-cache Now I can run the entire stack with just one command! :) Gitlab commit link @Pretbc Pretbc Do you want to do a code review?

Hello engineers, For the past few days I’ve been trying to set up Supabase as my backend‑as‑a‑service. It turns out it’s a bit more complicated than I expected (surprise :)). The goal is to set up a solid foundation for future development. I want to create tables for users and tenants. Supabase already has a table for users — auth.users. That table is for authentication: when a user registers in the app, a record is created there. But if I want to connect that user to other tables, I need to access the user’s id from the auth.users table, and it looks straightforward: just use auth.users(id). For example, if I want to create a table public.users (for storing additional data for each user), I can do this: CREATE TABLE IF NOT EXISTS public.users ( id UUID PRIMARY KEY REFERENCES auth.users (id) ON DELETE CASCADE, -- additional data for a user full_name TEXT, avatar_url TEXT, created_at TIMESTAMPTZ DEFAULT NOW(), updated_at TIMESTAMPTZ DEFAULT NOW(), tenant_id UUID REFERENCES public.tenants (id) ON DELETE CASCADE ); Now the user is fully linked to the app logic, while still being backed by Supabase Auth.

Hi! I’m a senior React dev and can help you ship this quickly and cleanly. I’ve built production apps with React/Next.js, TypeScript, and modern state/data tools (React Query, Redux/Zustand), and I’m big on performance + maintainable code.