how does your avo line in the

Gemfile

look like?

> bundle info avo * avo (2.30.0) Summary: Configuration-based, no-maintenance, extendable Ruby on Rails admin panel framework. (...) Path: /home/igo/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/avo-2.30.0

gem 'avo', "~> 2.30"

At bin/dev are a brew command, but I am in Linux. Maybe some settings are specific to MacOS?

2. or you'd like to run Avo 3 in your own app?

For scenario 1:

because avodemo is running

avo-advanced

which is a paid product, you'll need to purchase the avo advanced tier from here https://v3.avohq.io/pricing

Avo 3 is a different from Avo 2 as in all the paid features have been extracted from the Avo gem and moved to different gems as avo-pro, avo-advanced, and more and all those gems are available only to paying customers

After you'd get that tier, you'll need to follow these instructions to get the gem token on your machine and download the premium gems https://docs.avohq.io/3.0/gemfile-environment-variables.html

For scenario 2 where you'd like to get Avo 3 Community to your app, you'll won't need any gem server token, but just to add the path to your

Gemfile

so instead of

gem 'avo', "~> 2.30"

you'll need to have

gem "avo", ">= 3.0.1.beta9", source: "https://packager.dev/avo-hq/"

and run

bundle update avo

that will bring you to Avo

3.0.1.beta9

Do you think it would make more sense to keep it in your repository, and have more control to ensure the quality and integrity of the demos

Or they prefer to reference third-party repositories, in this case, without being able to guarantee the quality and integrity

the only step that is missing is to compile everything using

rake tailwindcss:build

you should be able to sign in and use Avo 2

The way I see it there are two types of demos. 1. One for "everything you can do with Avo" where we definitely should use avo-pro and avo-dvanced features. In that scenario we can't bundle the paid features in that repo because that would expose them to everyone. But we can provide de configuration files so anyone that has a valid license key can try them out 2. the second scenario is "Avo playground" where you can quickly clone a repo, run bundle install and without any license key you can play around with the features. Those features will be only the community version features, so it's not that useful in my mind

I wish there were an easier way to try and play around with all the features without exposing the source code. this is the difference of hosted and on premise software

#avo or #avohq?

# Avo

avohq.io is just the domain name. I couldn't find anything with just avo 😐

fun fact: Avo comes from Avocado. It was originally codenamed "project avocado" but again, no usernames available

I think #avohq is more direct, but I'll put #ruby #rails #avo. Suggestion for some hashtag

I intend to upload them all to GitHub and cite them in the articles, if that's okay.

The same erro after "rake tailwindcss:build"

$ rails db:migrate --trace ** Invoke db:migrate (first_time) ** Invoke db:load_config (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:load_config ** Execute db:migrate ** Invoke db:_dump (first_time) ** Execute db:_dump ** Invoke db:schema:dump (first_time) ** Invoke db:load_config ** Execute db:schema:dump ** Execute avo:build-assets Starting avo:build-assets yarn install v1.22.19 [1/4] Resolving packages... success Already up-to-date. Done in 0.02s. yarn run v1.22.19 error Couldn't find a package.json file in "/home/igo/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/avo-2.30.0" info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. Done $ bundle info avo * avo (2.30.0) Summary: Configuration-based, no-maintenance, extendable Ruby on Rails admin panel framework. (...) Path: /home/igo/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/avo-2.30.0

ok. we'll look into those too

thanks for reporting iut