Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 months ago.
Improve this question
I need a little advice before I start work.
So I have been developing a site under React for a client for 2 years now.
My client wants to duplicate this site to create 3 additional brands, the architecture, the design is the same, just the content and the logos change.
So for you is this:
1 - I duplicate in several github repos
Where
2 - I simply create several branches
Thanks
It really depends.
Option A, copy-paste your project to X other projects will make it easy to start and you can finish it in a day, BUT... every time you'll have to fix a bug you will need to do it in each repo and they'll diverge.
Option B, is to build front-end and an API.
The UI will be the same for all the projects but the API will return different data based on the client.
Option C, create a configuration file that you can modify based on the customer.
I believe that Option A will be the simplest & fastest one to get started with. You'll pay the price as you grow, but if you don't need to maintain the projects in the future I would go with it.
If you're going to maintain those projects for a long time you might want to consider refactoring the projects to a dynamic backend that returns the data based on the client.
Option C, it's a pretty good compromise between A and B.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 months ago.
Improve this question
I'm hoping someone can point me in the right direction. I would like to add the Metaplex/candymachine function to an existing website that was originally built to work with metamask. Just trying to save myself from having to redo the website. Thanks
There's no real easy way to do this unfortunately unless you have some prior HTML/CSS/and JS knowledge.
What some people do is take the logic from the CandymachineUI which can be found here CandyMachine.ts which is a type script file and port it over to their own website. You could also attempt to remake the UI calling to these functions and data, or failing that pulling the existing Mint area out the CandymachineUI site (built on React) and attempting to slot that into your existing site. I'd recommend if you took that approach that you swap out the MUI components for div's and your own CSS to save adding MUI to your site adding some bloat (unless your site already uses MUI then you good to go).
Bare in mind you'll also need the supporting dependecies too.
There are also other community built UI's out there but you are going to run into the same issues of porting over all the js/ts to your own site.
I always say it's generally quicker to rebuild a site around an already made mint template than it is to put the mint function into an original.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I'm currently developing a side-project and trying to learn some general API things.
The user can access a list of projects by going to /projects and I'll get
all of the projects as a list. The user can also click an Edit button that goes to
edit/{project_id} and was wondering whether I should pass the project object to the component or just do a separate request to the API with the ID of the project to only get that project.
The first one is good because it's easier and also, I won't have to send all information about the project objects because I can't show all of them in the table (in /project) and this will save some data (ex. the list will show name of project and created date only). However, the second way is good because there will be less requests to the server.
My question here is, what is the preferred way?
Sidenote: I've tried searching for a question like this but didn't know how to phrase it, so this might be a duplicate.
In this situation, I would advocate for the separate API request. With a list of projects, you really don't want to include everything in your "get all" API call; just enough basic stuff to populate the list. That will make your queries faster and data transfers smaller, which is especially helpful when a large number of projects come into play. However, when you "deep dive" into a single project, then you'll want everything about that single project.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
This question is a little more generic, a brainstorm one. I'm about to develop a small website, and I still don't know if it’s better for me to store my “Text” (to fill Labels, Messages, etc) data on the Database or just on the frontend.
I know that for a fact, consulting the BackEnd Database is slower than just searching a specific file, but it’s also better to update the list later-on (when the website is developed) by just running a script.
I want to know some opinions, experiences, advantages and disadvantages about both.
Edit: For the technologies, i was thinking in using ExtJS with a Java Backend, I'm not quite sure about the BD yet.
Consider what data you are storing and the purpose of your website.
Advantages of front end storage: quicker
Advantages of database storage: more secure/structured
If your strings are sensitive then I would secure them in your database. Any client information, including "Text" data should be stored on the back end. If the strings are only relevant to you as the site owner then I don't see a problem with storing them on the front end.
Also perhaps specify which technologies you are using to build this site to get more specific responses.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm currently building a Hybrid mobile app using ionicframework,angularjs and cordova,in my app i will need some data storage such as all users details.
What i'm trying to figure out is how to update the database for all users,for example if a new user signs up,he should be added to the database and everyone else should be able see his profile instantly,i'm thinking the database should be shared online instead of just updating the local database installed with the app,i'm currently using SQLite plugin to store such data but i'm not sure if it's the right choice for my case.
Does anyone know how to reach what i want ? i would appreciate any help.
Thanks.
Too many users then no point in storing and syncing. Creates more data inconsistency issues and resource consumption.
Online is the way to go.
If there is a subset of users whom u want to store information then thats an option.
Like watsapp stores and syncs information of those who are on your contact or chats only and not the whole watsapp db.
Thank you guys,after a lot of research,few days ago i decided to use Firebase,it's really powerful and works perfectly with angularJS and ionicframework which i'm using to build my app. I would really recommend it in situations similar to mine.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
First of all I don't mind the "writing more code" attitude that CI has so I don't really care about that. Right now I'm pretty good in CakePHP (I have like 3-4 years in it) and I think it has certain flaws the biggest one being its speed and I was thinking of passing over to CI but I need to know something..
My simplest application in CakePHP (with admin and some data in table - multilanguage) takes about 0.2 Seconds of code processing. I was wondering if anyone has a time for Code Igniter for a certain website. I'm curious if it's worth the learning time.
I installed code igniter and at first it seemed imensly fast but I'm just worried that if I keep adding components, models, helpers and everything to it it will slow down (maybe more than cake). So.. I'm actually looking for an example of CI website and the exact time it loads... (down to at least 2 decimals).
This thread will give you a fairly good answer, as the site in question is not a "Hello World" but a fully fledged Site with database access helpers and libraries loaded, etc...
I'm sure some will have arguments about its validity (probably CakePHP proponents), but it's not every day you have a site re-developed between frameworks and compared.
UPDATE
Again, for those that don't want to follow the link to the thread, the tester actually upgraded the site to CI 2.0, using modular extentions, caching, other optimizations and re-tested