Git Product home page Git Product logo

railsdevs.com's Introduction

RailsDevs

The reverse job board for Rails developers.

RailsDevs homepage

RailsDevs empowers independent developers available for their next gig. It is being built around three core values:

  1. Empowering the independent developer
  2. Doing everything in public
  3. Creating a safe, inclusive environment

Getting started

Requirements

You will need a few non-Ruby packages installed. Install these at once via:

brew bundle install --no-upgrade

...or manually:

  • Ruby 3.2.3
  • libpq - brew install libpq
    • libpg is needed to use the native pg gem without Rosetta on M1 macs
  • postgresql - brew install postgresql
    • Note 1: PostgreSQL 13+ is required
    • Note 2: In case you're on Debian 11 and you have multiple versions (e.g. 9.x, 12.x, 14.x) of PostgreSQL installed, make sure that the server of the right version (13+) is listening on port 5432. One could check/modify that in the postgresql.conf file, e.g. in case of version 13: /etc/postgresql/13/main/postgresql.conf.
  • node - brew install node
  • Yarn - brew install yarn
  • Redis - brew install redis
  • Imagemagick - brew install imagemagick
  • libvips - brew install vips
  • Stripe CLI - brew install stripe/stripe-cli/stripe
  • foreman - gem install foreman
  • Google Chrome + Chromedriver for system tests - brew install --cask google-chrome chromedriver

Initial setup

Start the PostgreSQL server.

brew services start postgresql

Start the Redis server.

brew services start redis

An installation script is included with the repository that will automatically get the application set up.

bin/setup

Development

Run the following to start the server and automatically build assets.

  • Requires foreman or overmind
  • Requires stripe
bin/dev

Seeds

Seeding the database, either via rails db:seed or during bin/setup, creates a few accounts. Most importantly, use [email protected] and [email protected] with password password.

More information is in the docs on seeds.

Stripe

You will need to configure Stripe or do a mock configuration (ie set dummy values for the last step listed below) if you are working on anything related to payments.

  1. Register for Stripe and add an account
  2. Download the Stripe CLI via brew install stripe/stripe-cli/stripe
  3. Login to the Stripe CLI via stripe login
  4. Configure your development credentials
    1. Create a Stripe secret key for test mode
    2. Run stripe listen --forward-to localhost:3000/pay/webhooks/stripe in order to generate your webhook signing secret.
    3. Create a product with a recurring, monthly price
    4. Generate your editable development credentials file via EDITOR="mate --wait" bin/rails credentials:edit --environment development. You may need to install and provide terminal access to the editor first (mate, subl, and atom should all work). If you run the code above and receive the message "New credentials encrypted and saved", without having had the opportunity to edit the file first, things have gone astray. You will need to troubleshoot this step based on your OS and desired editor, to ensure you can edit the development.yml file before it is encoded and saved. See here for more details.
    5. Add the secret key, the price, and your webhook signing secret to your development credentials in the following format, and save/close the file:
stripe:
  private_key: sk_test_YOUR_TEST_STRIPE_KEY
  signing_secret: whsec_YOUR_SIGNING_SECRET
  price_ids:
    part_time: price_YOUR_PRODUCT_PRICE_ID
    full_time: price_ANOTHER_PRODUCT_PRICE_ID

Monitoring

Application monitoring is powered by Scout APM. This helps identify N+1 queries, slow queries, memory bloats, and more. Scout APM is free for open source.

Testing

  • Run rails test to run unit/integration tests.
  • Run rails test:system to run system tests, using headless_chrome.
  • Run HEADFUL=1 rails test:system to run system tests, using headful_chrome.
  • Run bin/rails verify_mailer_previews to verify mailer previews.

Changelog

Significant changes and product updates are documented in the changelog.

License

All code and documentation are copyright 2023 Joe Masilotti under the MIT license.

All other resources including, but not limited to, images, copy, and branding, are copyright 2023 Joe Masilotti and used by permission for this project only.

Open source support

RailsDevs uses a free or discounted open-source plan from the following companies. Thank you for the support!

Scout APM – application monitoring

Scout APM logo

Papertrail – log management

Papertrail logo

railsdevs.com's People

Contributors

adrienpoly avatar axhgl avatar caseyjenks avatar dependabot[bot] avatar dhairyagabha avatar fig avatar galtdea avatar gathuku avatar heliocola avatar hungmi avatar imella avatar jespr avatar jkostolansky avatar joemasilotti avatar joshio1 avatar kaushikhande avatar lsparlin avatar mansakondo avatar metamoni avatar mikerayux avatar padi avatar patrickmcsweeny avatar rayhanw avatar robzolkos avatar salochara avatar sarvaiyanidhi avatar themudassarhassan avatar tonksthebear avatar troyizzle avatar ypcethan avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

railsdevs.com's Issues

Migrate to railsdevs.com 🥳

Is your feature request related to a problem? Please describe.

I recently purchased railsdevs.com and want to transfer of the site.

Describe the solution you'd like

Visiting railsdevs.com renders the current site. Visiting railsdevs.io or www.railsdevs.io redirects to railsdevs.com.

Describe alternatives you've considered

Keeping the .io.

Restrict outbound links to signed in users

Currently, the Message button is hidden unless you are signed in. Clicking it opens up your email client with the developer's email populated.

Instead, I want to route the click through our servers. That way we can track when an outbound link is clicked and we can authorize the user (instead of showing it / not showing it).

I'd also love to see all external link (GitHub, Twitter, website, etc.) follow this same approach. Once we get it set up for one link it shouldn't be much more effort to extract to others.


The long term goal of this issue is to start charging companies to get in contact with developers.

Users who already have a developer profile can create a new one

Users who already have a developer profile can create a new one despite already having a profile. This can create a confusing UX when the following happens:

  1. A user mistakenly clicks "Create a profile" thinking they're logged in.
  2. Realizing they are not logged in, the user logs in.
  3. The log in controller attempts to re-direct the user to their previous location.
  4. The user is now on the screen to create a new profile even though they already have one.

Determine the interaction of direct uploads with ActiveStorage validations

In #20 I opted to use a direct-upload approach. active_storage_validations can handle this, but things get a bit complex. On one hand, it's obvious that if the validations fail, it won't attach the image. For instance, the file doesn't become part of the model.

That said, I was still seeing an upload notification in server logs. This begs the question, what's happening? According to the repo, the author of the gem isn't sure either. We probably should do some investigation ourselves in order to determine what we have to do to keep the database clean.

Add tests for avatar and cover photo uploads

We need to determine how we're going to go about testing the avatar uploads in #20. This breaks down into basically two items.

  1. Are we okay with using shoulda matchers? This is the recommended way to test file attachments according to the active_storage_validations gem. I've never personally used them.
  2. How do we handle file fixtures? I need to do some investigation to figure this out, but I wanted to put it out there in case anyone else knew.

Add rate and/or salary to developer profiles

I'd love a way for developers to show their expected rate or salary, optional of course. One way would be to do ranges; a min and max for each. The other approach is to set an expected target as a single number.

I'd love feedback on this from folks! What would you rather fill out on your developer profile?

A business can message a developer

The first second (of many) Messaging issues!

A PR addressing this issue should...

  • Add a Message button to a developer's profile
    • When clicked, if signed in as a business then open a new conversation screen
    • When clicked, if not signed in as a business then prompt to create a business profile
  • developers/:id/messages/new with an input field
    • Create a Conversation that belongs to the developer and business
    • Create a Message that belongs to the conversation
    • Can only be access by a business (via pundit)
  • conversations index of all conversations the developer or business is a part of (read only)
    • Link to conversations from header / menu
  • /developers/:id/conversation show a specific conversation (read only)
    • pundit for authorization scopes
  • Hide the Message button in production based on the feature flag
  • Double check mobile views

Production!

After 60 days I will transfer the domain to namecheap. Apparently you have to wait that long to transfer a new registration.

areas of developer interests

Regarding our recent conversation here #45 I suggested to implement something like limited badges, that developers can choose

Additionally, I think it might be useful to add some preferences between the two options, it can help to better understand developer preferences.

For example:
ruby - other backend languages
rails way - dry-rb

I don't know maybe developer can set some percentage proportion 30/70 or 50/50 or something like this

It can helps employees to choose developers that better match their project conditions. For example, it's good for big projects that currently rewriting their existing monoliths to microservices with golang backend language, that your future ruby developer has some interest in golang. And vice versa for startups it's not valuable if the developer starts to push founders to try any other technology only because he has an interest in it.

A developer can reply to a conversation

A PR addressing this issue should...

  • A developer can view their conversations via a link in the nav bar
  • A developer can view individual conversations via the conversation list
  • When viewing a conversation, there is a text field to reply to the conversation
  • On form submit, aMessage is created
  • Messages are correctly identified as being sent from "You" or the business/developer

Add filter developers by Availability

This will be easier to find the developer by their availability

Here's the time range I propose:

  • All -> this is the default one
  • Available Now
  • In a week
  • In two weeks
  • In a month
  • More than a month

Add site purpose/description

Folks coming to the site without knowing anything about it are a bit confused. I'd love to add the following copy in a header (or similar) on the home page.

Find Ruby on Rails developers looking for freelance, contract, and full-time work.

The tricky bit here is that the layout/design of the page needs to change to incorporate this. I'm open to mockups and PRs on this one and could use some help!

To-do

  • Redesign homepage to add description
  • Mobile redesign of homepage + menu
  • Developers#show
  • Devise forms (sign in, registration, passwords, confirmation, etc.)
  • Flash message
  • Footer with links to open source repo, analytics, and creators (for now)

Add system tests

I think the app was setup in rails new to not have system tests (but I'm not sure).

Do you want system/browser tests (if so I can add to CI)

Should handle ActiveRecord::NotFound exception and display a nice UI for developer not found page

Describe the bug
We are using find method which will throw ActiveRecord::NotFound exception if record with the specified id not found

To Reproduce
Steps to reproduce the behavior:

  1. Navigate to any developer profile that doesn't exist for example https://www.railsdevs.io/developers/1000

Expected behavior
Should handle that exception and show a nice UI of developer not found with specified id or something like that.

Screenshots

Screenshot 2021-11-18 at 2 05 29 pm

Additional context
Add any other context about the problem here.

Badges!

I want to display badges on developer profiles that are verified via an automated system.

The first one is a contributor to this project. Using the GitHub API, we could check this repository's contributor list and cross-reference that with the developer's username.

Once we have that system in place, it shouldn't be much more effort to add the same functionality for the Rails repository.

The big lift here is OAuth with GitHub to ensure someone has access to the GitHub account they say they are.


What other badges would you like to see on your developer profile?

Setup the production environment to take file uploads

In #20, I setup the app to handle file uploads on the disk for development and test environments. In order to push to a live system, we'll need to configure a remote service to accept uploads. I don't know what you want to do with this @joemasilotti, but I wanted to open this issue to field what you're thinking.

Open Graph meta tags

  • title and twitter:title
  • description and twitter:description
  • image and twitter:image – hoping to integrate Mugshot Bot for dynamic images

Move all copy to translation (locales/en.yml) file

Describe the bug

Not really a bug, but more a chore. We should move all of the copy to the i18n file config/locales/en.yml. This will make our lives much easier if/when we translate to a new language. It also keeps everything in one spot vs. littered across the app.

Mobile menu z-index is off

Describe the bug

The mobile menu is covered by elements on the Developers#show page.

To Reproduce

Steps to reproduce the behavior:

  1. Visit any developer page (e.g. https://www.railsdevs.io/developers/1) on mobile
  2. Open the menu
  3. See the avatar and hero covering the mobile menu

Expected behavior

The mobile menu should be on top of everything.

Screenshots

image

Support for Timezone setting for the dev profile

As a developer based in EU I want to be able to select my TZ so that potential clients can figure out if I match their timezone enough when looking at my profile.

UI bits

  • when editing a developer profile, display a select box with TZ to select from using City, Country "Paris, France" and UTC reference "UTC +/- 1".
  • when showing a developer profile, display the timezone.

Questions

  • is it worth digging into the whole "where are you based?" with country too ?

Interested in linting erb with standardrb?

Love that this project uses standardrb. How about linting your erb files too?

I recently set up a new Rails app with a pretty minimal erblint config using standardrb for embedded ruby code. Happy to contribute PR if desired!

cat .erb-lint.yml | pbcopy
👇

---
EnableDefaultLinters: true
linters:
  ErbSafety:
    enabled: true

  Rubocop:
    enabled: true
    rubocop_config:
      require: standard
      inherit_gem:
        standard: config/base.yml
      AllCops:
        DisabledByDefault: true
      Style/IdenticalConditionalBranches:
        Enabled: false
      Layout/BlockAlignment:
        Enabled: false
      Layout/HashAlignment:
        Enabled: false
      Layout/IndentationConsistency:
        Enabled: false
      Layout/InitialIndentation:
        Enabled: false
      Layout/IndentationWidth:
        Enabled: false
      Layout/LeadingEmptyLines:
        Enabled: false
      Layout/ParameterAlignment:
        Enabled: false
      Layout/TrailingEmptyLines:
        Enabled: false
      Layout/TrailingWhitespace:
        Enabled: false
      Lint/Void:
        Enabled: false

Document all expenses

Is your feature request related to a problem? Please describe.

Being an open product, I want to document all expenses involved in running the site.

Describe the solution you'd like

I want to see these expenses on the website and linked from the header. Perhaps /open or /stats could work in the long run. But for now something simple like /expenses is probably fine.

Describe alternatives you've considered

None, yet.

Additional context

To keep track until this feature is built, I will document all expenses here.

Expenses

  • October 21 - purchase railsdevs.io, railsdevs.org, and railsdevs.online - $49.33
  • November 12 - Fathom analytics monthly - $14
  • November 13 - purchase railsdevs.com - $250
  • ...

Pending expenses

  • December 9 - hosting on Heroku - $7

Reset password does not work

Reset password does not work.

Steps to reproduce the behavior:

  1. Go to 'https://www.railsdevs.io/users/sign_in'
  2. Click on 'Forgot your password?'
  3. Enter provided email address
  4. Click on Send reset password instructions
  5. It raises this validation error Invalid Email or password.

Expected behavior
After clicking Send reset password instructions button, it should send a resetting password instruction email I guess.

Add rspec as test library

What do you think about to add the rspec library, Factory bot, Shoulda matches?

i can do it if we need it

After signing up, a user can identify as a developer or business

A PR addressing this issue should...

  • After signing up, present a new screen asking if the user is a developer or client at /roles/new
  • If a developer, redirect to developers/new
  • If a client, redirect to businesses/new
    • This form includes name, company, and avatar

Long hero causes page to scroll horizontally

Describe the bug
If a developer enters a very long Hero then the page shows the entire content and causes horizontal scrolling.

To Reproduce
Steps to reproduce the behavior:

  1. Visit the homepage on mobile
  2. Scroll down to the developer in the screenshot

Expected behavior
The page doesn't scroll horizontally.

Screenshots
image

Additional context
This can be done in CSS but I'm not 100% sure which property to use.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.