property_web_builder

Create a fully featured real estate website on Rails in minutes! ⛺

Runssource: GitHubhomepageRubyMITcommit 34ed1756762b

Ruby, MIT licensed. The project labels itself: cms, crm, heroku, lead generator, mls, opensource, property management and proptech.

property_web_builder runs. An Argusic agent installed it in 34 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

From-source user-local Ruby 3.4.7, PostgreSQL 16.9 and Redis 7.4.3 run PropertyWebBuilder 2.2.0: full RSpec suite passes (7424 examples, 0 failures, 77 pending) and the Rails dev server returns HTTP 200 with a seeded homepage, property detail, buy listings, public API JSON and the /health ok payload.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.11 (measured)
recorded runs
2
last tested
stars
652
forks
288
open issues
42
watchers
38
size
95 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing property_web_builder, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • No Ruby/Postgres/Redis in container; system packages unavailable (no root)22 minutes
  • pgcrypto.so failed: undefined symbol EVP_cast5_cbc (system OpenSSL 3.0 has no CAST5 without legacy provider)9 minutes
  • Localhost root redirected to /setup in loop after seeding because find_by_host could not resolve the default website6 minutes
  • pwb:db:seed_tenant[default] crashed with 'Please provide valid page_part_key'5 minutes
  • Tailwind build failed: Cannot find native binding @tailwindcss/oxide-linux-x64-gnu (npm skipped optional dep, Node 18 below engine requirement)3 minutes
  • Failing spec: seed_runner updated_at nanosecond vs Postgres microsecond precision2 minutes
Install time
34 minutes
Cold machine to finish
54 minutes
Errors hit and fixed
7 hit, 7 fixed with no human help
How the result was proved
bundle exec rspec exited 0 with '7424 examples, 0 failures, 77 pending'; curl http://127.0.0.1:3000/ returned 200 (106433-byte seeded homepage); curl /health returned 200 {"status":"ok","pwb_version":"2.2.0"}; curl /api_public/v1/properties returned 200 JSON; curl /en/buy and a property detail page returned 200
Model tokens used
2,015,741
Exact commit tested
34ed1756762b
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- Installed gems (`bundle install`) and npm packages (`npm install`), built all 6 Tailwind themes, …
- Found and fixed 4 real bugs; the full test suite went from 1 failure → **7424 examples, 0 failure…
- Launched the app (Puma, `http://127.0.0.1:3000`) and exercised real HTTP: `/` 200 (106KB seeded h…
**Changes**
- `app/controllers/pwb/application_controller.rb` — include `LocalhostDefaultWebsite`; localhost ro…
- `app/models/concerns/pwb/website_domain_configurable.rb` + `app/models/concerns/website/domain_co…
- `lib/pwb/contents_seeder.rb` — skip orphaned page parts (from other websites) during seeding inst…
- `spec/lib/pwb/seed_runner_spec.rb` — reload the user before snapshotting `updated_at` (Ruby ns vs…
- `package.json`/`package-lock.json` — added `@tailwindcss/oxide-linux-x64-gnu` (npm skipped it: en…
**Gaps (recorded, not fixed)**
- `@playwright/test` 1.61.1 needs Node ≥20; could not run the e2e suite (only RSpec).
- `EVP_cast5_cbc` symbol needed the OpenSSL legacy provider; requires `LD_LIBRARY_PATH=/home/runner…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 34 minutes to install, slower than the median of the 29 comparable projects Argusic has measured.

Of the 30 cms projects Argusic has installed and timed, property_web_builder was the 29th fastest to reach a running state, and 27 of 30 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.11
Argusic Runner1/3Did not run20.000.00

Topics (from GitHub)

cmscrmherokulead-generatormlsopensourceproperty-managementproptechrailsreal-estatereal-estate-websiteretsruby

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/property_web_builder.svg)](https://argusic.com/subject/property-web-builder)

Questions

Does property_web_builder run?
Yes. property_web_builder runs. Argusic installed and launched it on a clean machine in 34 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test property_web_builder?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 34ed1756762b. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test property_web_builder?
The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does property_web_builder take to install?
34 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does property_web_builder need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing property_web_builder?
7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does property_web_builder compare with the alternatives?
Of the 30 cms projects Argusic has installed and timed, property_web_builder was the 29th fastest to reach a running state, and 27 of 30 reached one at all.
Where is the evidence for property_web_builder?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion