* feed cards * frontend * preactify * preactify * . * fix * fixing things and adding dropdown * whoops. * whoops 2. * revert body bg color change * search snippet * search snippet * get rid of featured article * get rid of featured article... * cover to its own component * videos * videos * reading time * small-save-filled asset * author adjustments * adjustments * Author --> Meta * whoops. * loader * logged out state * . * dropping what's not needed for now * better name for cover * get rid of nav overflow * bringin comments placeholder back * bringing comments placeholder back * publish date * fix * date * . * save button icon * ghost button * lets skip the icon for saving for now * more buttons * counting logic * Display top comments on homepage feed * Comment list and item components * Remove 'Top Comments' title * Remove subscribe button, add reading time * Update snapshots and tests * Fix article and follower scrolling * Added reading time * (Try) to do flare tags * Button component from Pawel * More button styles from Pawel * Comment count style from Pawel * Handle empty parens for age on older articles * Dont show 'more comment' button for more than 2 comments * cover ratio * flare tag * cover fix * fix buttons * more button fixes * tags fix * responsiveness fix * reading time + a bit of responsiveness * Reading time in more places * snapshots * default color for flare tag * Update CommentsList test snapshot with new styles * fixing search results * fixing buttons * Fix podcast card tests by updating snapshots * Line clamping for top comments * Reflect save button state after click before mouseout * Now the entire feed card is clickable. (#7638) * Now pointer cursor is only on feed posts. (#7727) * Revert podcast card styling * Update test snapshot * merge * Fix rspec on feed page * Reduce complexity of class check for feed card clicking * PR feedback/fixes * Fix featured article test and snapshot * Last minute test tweaks * clean up crayons * padding issue + empty div * Correct merge error * Fix search results tests * Test fixes and snapshot updates * themes * podcasts colors Co-authored-by: ludwiczakpawel <ludwiczakpawel@gmail.com> Co-authored-by: Nick Taylor <nick@iamdeveloper.com>
41 lines
1.8 KiB
Markdown
41 lines
1.8 KiB
Markdown
---
|
|
title: Self Hosting DEV
|
|
---
|
|
|
|
## Hosting your own DEV instance
|
|
|
|
We envision that the DEV codebase will eventually be generalized to the point
|
|
where it can be used to power other communities and ecosystems. We're excited
|
|
for the project to mature to that point, but we're not quite there yet.
|
|
|
|
This page is designed to serve as an FAQ and a checklist of considerations that
|
|
are relevant to the goal of eventually hosting your own version of our community
|
|
platform.
|
|
|
|
### Current limitations
|
|
|
|
- We do not currently have a versioning system that will allow us to share fixes
|
|
and improvements with modified versions of the code.
|
|
|
|
### License restrictions
|
|
|
|
- Certain aspects of the app are currently hardcoded. For instance: logos,
|
|
certain elements of content, etc. If you were to host the current version of
|
|
the app, you would be inadvertently impersonating the core dev.to project.
|
|
- DEV has commercial licenses for certain design components as described in our
|
|
[Design License Info](https://docs.dev.to/design/branding/#design-license-info)
|
|
section. These licenses are specific to the dev.to project, and may not extend
|
|
to self-hosted versions.
|
|
|
|
### I want to stand up my own entity using the DEV codebase, how can I help?
|
|
|
|
- You can help us to generalize the code by removing DEV-specific language and
|
|
images and replacing them with environment variables or database tables as
|
|
appropriate
|
|
- You can commit to staying in very close coordination with us as we navigate
|
|
the process together.
|
|
|
|
The long-term benefits of doing this the right way far outweigh the short-term
|
|
gains of spinning something up without consulting us. If you are interested in
|
|
getting started with this process, let us know in
|
|
[this thread](https://dev.to/ben/so-you-want-to-stand-up-your-own-instance-of-dev-help-thread-1elo).
|