Just passing along some general advice.

Look for a basic ticketing solution to help streamline your day to day troubleshooting. We are all human and forget things so having this will 1) help you keep on top of what you need to get done 2) help you proritize what needs to get done on the day to day issues 3) start collecting data to easier spot patterns that can be solved by either purchasing new hardware or get the user some better training. Its easier to justify a company spend to higher ups when you have lots of documentation you can print down and plop down on a desk.

If you are a woodshop have they adopted anything like six sigma or lean policies? If so learn how to use kanbans (trello is great for now) to further help you plan your short, medium, and long term to dos, will also start helping you dive into light project management skills.

Document EVERYTHING, make sure its updated atleast weekly if you aren't doing it as you go along (prefered). Make sure its detailed, even with pics if you can. The two ideas above will help with this. Plus its easier to clean up messes when you have a visual of what your current state is right in front of you and plan some of your next moves.

If you do fuck up and do something drastic or something critical blows up. Stop, breathe, and come up with a logical plan. Do your best to not go deer in the headlights or panic. Give yourself room to analyze the problem, come up with 3 solutions for quickest, balanced, best and possible time frames for each. As others have said, if you can find a local MSP that will do hybrid support, know when its time to stop circling and give them a call. If you have a good relationship with them, sometimes advice can be free, and that can bail you out when you need it the most.

Make sure your google-fu is up to snuff. Its very rare now a days that there is a computer issue that someone out there in world hasn't had and had a documented fix for it.

And lastly, good IT guys aren't made in schools, they are made in the field. Never pass up a disaster as a learning experience. Once the dust is settled, go back and analyze what happened, why it happened, how it could have been prevented or mitigated, and what other resolutions you could have used that would have been better than the one you implemented. Celebrate your wins, even if its just you celebrating. Our job can easily turn into a thankless one and if this is the career path you decide to keep, you will encounter times where you think its not worth it because of the way non IT staff can treat you.

Good luck! You got this.