Answer the question
In order to leave comments, you need to log in
Should a layout designer be able to raise a server and deploy a project on Linux?
Hi) The situation is like this I got a job as a layout designer, on the first day they told me to deploy a project locally on php, nginx, mysql, etc. Are these adequate requirements, layout designer? Can you advise how to quickly learn this?)
Answer the question
In order to leave comments, you need to log in
Typesetter - must be able to set up and configure his working environment in order to typeset.
That is, to engage in their direct activities.
And nothing more.
Next - we read the organization's regulations, duties for the vacancy and draw conclusions.
Look at it from a different angle. There are no strictly defined criteria for what a layout designer should be able to do and what not. Each company has its own. And it is in your interest to be able to do what is needed for most companies in the market. Specifically for this, you must be able to raise the server. And in the other you will have to work with git. And in the third to communicate in German. And somewhere you may not be hired, already because your communication skills are weak, and it is not comfortable for others to work with you.
If at the interview stage you didn’t lie about yourself, then your employer knows perfectly well that you don’t know how. In this case, you may well approach a senior developer and ask them to tell you about the internal stack, how to raise servers, what libraries, tools are used, what versions, and so on. To show you everything, tell and teach.
they say I should be able to do it, raise a server, etc.I work as a PHP developer, I don't know how to work on Ubuntu and I don't want to. When it is necessary to deploy something on *nix-like systems, I write a letter to specialists in a group called UnixAdmins and they do it. And that's okay. My task is to develop a project, not to tinker with servers.
deploy locally on ubuntu a project on php, nginx, mysql, etc .... they say I should be able to do this, raise a server, etcNo, it shouldn't. It would certainly be a useful skill, but you're just a junior frontend.
Can you advise how to quickly learn this?)No way. It will be a stupid copy-paste from the manual without understanding. And understanding comes only with years of experience.
Probably won't pass probation.yes, to hell with them.
Absolutely not, from the very concept of "impositioner", it is already clear what he should do.
A web site designer is a specialist who creates full-fledged HTML pages from a drawn design.
Should/should not be an efficient approach.
If you want to advance at least a little in the profession, you must be able to learn new things. The thing about getting a server up is a basic skill, you can of course look for some people who "should" do it for you and be inordinately officially right, but it's much better to figure it out and be a little cooler.
Otherwise, there will be stagnation, like some characters who "are not obliged to do their job," and at the same time, in neighboring topics, they whine that there have been no glimpses in their career for 10 years already, the salary is somehow beggarly, and there is nothing but to swell hating everyone around remains.
If this option does not suit you, then take the manuals and go ahead. There are many good ones, for example https://www.digitalocean.com/community/tutorials/h...
Then you go to the toaster with specific problems and not questions like "they make me work more than expected."
The most ideal option is to approach someone who has already raised this project and ask for help.
Even if you figure out how to raise a server, there can always be some nuances that are needed specifically for this project and which you simply cannot know, but it’s right to come up and ask.
You should be able to set up a working environment. If this involves setting up a Linux server, then they should.
Here gathered, mainly, sooo narrow specialists. Not being able to do the simplest things is a shame. It was necessary for the company to hire a specialist for each html tag. That would be great.
Are these adequate requirements for the front, layout designer?
My opinion ....
1. Customers want to save on the administrator. junior frontend can and should be able to deploy a LAMP server, but not a junior frontend .
2. Either you do not finish what you promised to the customer))). It happened - "We will make you a website, give us good internet and a powerful server"
You still decide on a layout designer or frontend.
https://roadmap.sh/frontend
There are no strictly defined criteria for anything like that, but you, as a developer of any stack and level, should be able to raise at least your portfolio in the form of layout somewhere outside the local area, you don’t show the code / screenshots to everyone you will.
Frontend and layout are two different things. The frontender should be able to configure the server, but should not raise it, this is what the admin does. Here you set the listen 0.0.0.0 parameter in mysql and go! It works))
In general, in the office there should be at least an admin. And where there is a devops - they won’t even give you access to the project, you will push the code into the git and that’s it. If you are a June, it is even possible to request a commit.
And in general, in what kind of place does the frontend communicate with mysql directly? Give the name of your office or projects, I can pentest and say they are bullying you or you really have front-end junas part-time admins
The office is a rare schmuck, they could at least help, it is immediately clear that the team is rotten. The author write the name of the sharashka so that I know who to spit on when we meet.
well, it’s like I understood it once and forever, you can do one to one for any video lesson and that’s it
https://habr.com/ru/post/306716/
In general, yes. After layout, projects are pulled onto the engine and, firstly, they need to be done in such a way that there are no problems with the backend later. Well, after stretching, projects are developing, you need to complete / fix bugs.
For the first time, ask the developer to show how the project unfolds, where the necessary files are, and so on. Ask for documentation if available. If they do not help, there is nothing for a newcomer to do in such a team.
Can you advise how to quickly learn this?)
Get everyone up!
You are confusing the concept of "coder" and "frontend", but your employer is not. Read the article about what frontend should be able to do. You can figure out how to raise the lamp in an hour according to the instructions, in two days it was possible to make a server with all the goodies.
A coder is absolutely != junior frontend. And the Junior frontend should be able to raise it, or at least know how and where it is looked for so as not to stare like an animal with horns at a new building :) But the layout designer - no, the layout designer may well say - I have nothing to typeset, give me a working tool :)
In general, if there are no problems, then the bubunt and everything included in the lamp rises quite well in two days, especially if on a virtual machine.
in the question it is indicated that it is necessary locally. xampp is installed on Linux, opt/lampp/htdocs is rummaged and that's it.
According to the law, a "impositioner", "slinger", "digger" and in general any "-schik" must know how to and do exactly what is written in his job description and links from it to other governing documents. That is what he is paid for and nothing more. According to the concepts, a typesetter should be able to LAYOUT. "Rise" of servers is not and never was the responsibility of layout designers. This is the prerogative of "system administrators" and others like them. Crazy effective managers who have unsubscribed here with crazy texts in the comments, of course, may think otherwise. But these are only their wet dreams and nothing more. If a person is good at raising and setting up servers, then he knows the layout badly: people with a rubber head are extremely rare.
Personally, my position is that the more layout designers will raise servers, the more paid work for me and my colleagues, which is not bad. The fact that most of our "dynamically developing" sub-companies do not understand this and will never understand this should not be your difficulties as a specialist. In fact, few people can competently organize the work, everyone can only demand some kind of nonsense and try to plug holes "with what they have", which, in fact, is happening with you. In your place, I would seriously think about the expediency of working in such an "organization". As experience suggests - with such an "approach" there will be no way. Everyone must do their job.
I work as a system administrator, yes, yes, I am one of those who puts you servers for development and not only. Let's just say 5 years .... back and until 2019, we made servers for our maids ourselves at their request, ordinary lamps. But somewhere in 2019 or a little earlier, the juniors started doing it themselves or doing it on the docker. When asked why they usually answer yasamsus, then after the newcomers and crap they run with a cry of a cue ... well, the layout designer should not, but he can make lamps for himself even in the same docker or vagrant. The most important thing then is to give a look to the system administrator so that it would not be excruciatingly painful. If I were you, I would lift the docker and wind everything up there. If you did what you asked .. but already how ..... my yours don’t understand, I’m not a professional system administrator. Why docker? Because there are a couple of commands, that is, there are already ready-made lamps there. And in general, I advise you to look towards Ansible. The main thing is not to stand still, you need to grab a bit of related knowledge, if your faucet leaks, you will call a plumber or just dismantling the crane box, replace the gasket or the mechanism itself .. which costs 200 re on the market or in the construction market? Faced with a problem, one should at least not understand, and if one has the strength and the opportunity, one must strain. And yes, don’t forget, new generations will be able to roll out lamps for themselves .... so it’s worth learning how to make a platform for yourself at least from a docker. and if you have the strength and opportunity, you need to strain. And yes, don’t forget, new generations will be able to roll out lamps for themselves .... so it’s worth learning how to make a platform for yourself at least from a docker. and if you have the strength and opportunity, you need to strain. And yes, don’t forget, new generations will be able to roll out lamps for themselves .... so it’s worth learning how to make a platform for yourself at least from a docker.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question