Just checking: Is the policy on the admin to soft-delete via the paranoia gem, but never to restore, only create new clones of deleted items? (Context: I’m working on a process to control product data from another system; the current approach is to import changes; keeping the behavior as close to default solidus seems like a good idea.)

Hello everybody, my question is a bit off-topic but I'm looking for a SaaS (API) that helps me to find high quality images from a given text, all this texts are product names. I.e. "NIKE Dunk Low SE" or "Jack Daniels 40% 1L"

Any recommendations?

ElaticSearch

Just load whatever you're searching for into ES and you'll be surprised at how nifty this cheap trick is.

Hi community, another beginner question, I’m customising Solidus for my private project, assuming some will be in the forms of extension, some may need to modify Solidus gem’s source code (if possible, contribute back). I already forked Solidus to a public repo to sync with official Solidus repo, and a private repo for my own private project. My question is, if I use/modify Solidus in this way, how should I setup and run my private project? Option 1: use my public repo as the gem source for Solidus. Anything I made for Solidus has to be public immediately. All the private development need to be extension only. Not ideal.

rails new your_solidus_project_name --skip-javascript
cd /path/to/your-solidus-project-name
# in gem file, add solidus with reference to my public fork
gem 'solidus', github: 'my_public_fork_of/solidus'

Option 2: similar to option 1, but pointing solidus to a (local) private fork (not sure this is supported). But it also makes the development work happen in two places: the private project repo and the private fork repo. Not ideal. Option 3: I’m thinking somehow, I can modify Solidus directly in my private repo, either in the form of new extensions or to the source code of Solidus directly. My question is, how to run the project in development and release mode? by creating an sandbox as described in the “Develop Solidus” doc?

git clone <git://github.com/solidusio/solidus.git>
cd solidus
bundle install
bin/sandbox
env DB=postgresql bin/sandbox
cd sandbox
bin/rails server

Really appreciate if I could get unblocked by this. Thank you.

I'm curious why you think you need to fork Solidus. In previous projects with Spree, I've gotten into a bad state by doing so - it's really easy to let that fork drift and eventually end up with something unmaintainable.

I might suggest just ... not forking, and using monkey patches/extension hooks to customize the core Solidus pieces for your project. And if you find patches that seem generally useful, maybe consider upstreaming those?

fork so that i can create pull request to source repo, but it’s not necessary now.

if just patching the core directly, how to run the project?

for development and release

You reference the GitHub repo of your public (or with a little extra work, private) fork of Solidus from your Gemfile to run your app against it.

Totally random question that I'm curious about. For a product with variants, when managing stock, it looks like the master variant is still shown. Is that expected? Seems a little bit odd, but maybe I'm misunderstanding some use case.

I had thought that if a product had variants, that basically indicated that the master variant could never be purchased. Have I messed up my understanding somewhere?

No, your understanding is good. There's no use in showing the master variant on that screen for products with variants in a normal store. It was probably just simpler to show

@product.variants_including_master

for all products.

Friendly reminder if the maintainers have returned from vacation

Hi Solidus community, i got a seemingly weird request but i wanted to support Solidus community and got less biased help/opinion -- anyone available for helping me resolve the installation issue of Spree? i'm willing to pay some consultation fee if your hour rate is affordable 🙂

the issue as reported here https://github.com/spree/spree_starter/issues/968

Hi community, i'm stuck at choosing Spree, Solidus or Vendure to my multi-vendor project (like Amazon, each vendor has their own store page and manage their store separately). Think i can share what I learned on these three frameworks, please feel free to chime in meanwhile I'm also looking for some tech consultancy service to help me pick one & kick start the project. 1. Spree: a. documentation is not as comprehensive and passionate as Solidus b. claimed to be multi-vendor ready with their demo site, but i cannot run their project locally. So far didn't manage to get it solved or got support from the community or maintainer for 3+ days. c. more features than Solidus but the UI is not on par d. No Vue Store Front integration out of box but some ground work is done by Vue Store Front e. Ruby on Rails developers might be harder to find than Node.js developer 2. Solidus: a. documentation is great, setup process is smooth b. but no built-in support for multi-vendor, solidus_marketplace gem cannot be used as its dependency depends on an older Solidus core (<v3). c. admin UI is sleek d. No Vue Store Front integration out of box e. Ruby on Rails developers might be harder to find than Node.js developer 3. Vendure a. a relatively new project, based on Node.js stack b. documentation is great, setup is smooth even without any node.js experience c. no built-in support for multi-vendor but single vendor could have multiple channel with a single stock info for a product d. Vue Store Front integration is working in progress by Vue Store Front and to be release soon e. Node.js developers might be easier to find, with Javascript for both frontend and backend

I really like Solidus's sleek UI and ease of setup, but may not have time to develop the multi-vendor support, not sure its complexity too

hi #C0JBKDF35 - a couple of years working with solidus, happy to see you all here

somebody already able to set up the new version with rails 6 and its new active_storage as image attachment, did you manage to get the connection with AWS S3 sorted out?

Are you running into a particular issue?

I can upload the images into my bucket but I cannot see the image into the product store

I can see as well the link of my image into S3 but when I try to copy and paste into the browser I read an xml saying not authorized. My bucket is publit

public

are the objects themselves public? are the URLs the public urls or signed URLs?

signed

objects are public on AWS (I tried GCS as well)