Hello, how are you?
Currently, I am building a symfony project(symfony 5.4).
I am going to write a standalone upload script to upload backup files(.zip files) automatically to OneDrive.
And the files are up to 5 GB.
But I am not sure what should I start from and how to implement it.
If someone who has experiences in it, please let me know the way.
Any comment or suggestion will welcome.
Thanks.
In the spirit of open source, whenever you need a specific requirement, most probably someone else has published a library for it. You are in luck because there is already https://github.com/krizalys/onedrive-php-sdk. You can either use that library or reverse engineer from the source code to implement into your Symfony code base.
Related
So, this might be a stupid question. Bear with me, I'm new to CMS usage :P
Anyways, I'm using Bolt CMS to create a very simple website. For it, I just need a simple contact form, which means my server needs to be able to send out an email. I want to use PHP for this.
Now, how exactly should I handle this with Bolt CMS? The default configuration does not allow .php files to be uploaded, however I could easily change this in the main configuration, to allow for its type. My first guess was to try and upload it to either the theme folder, or the file folder for the theme. However, when I try to upload .php files they don't even show up in the folders I upload them to, even though it says the file was uploaded successfully. However, I'm unsure this would even be the best way to handle PHP scripts with Bolt CMS.
Anyone got any inputs to this? :)
Thank you!
For security reasons, Bolt will not allow you to run PHP scripts from inside Bolt. If this is something you need to have, there are two options:
Make it standalone. Create a contact.php on the server that handles it, and link to that.
The better solution would be to use an extension for that. Simpleforms (easy to implement, with a fair share of options), BoltForms (more options and allows for more control over the fields as well as uploads) or Simple Contact Form (very bare bones, but might be what you need).
I am new to Github, and want to find some good written PHP website application source code to read. But simply type 'php' as keyword and search on Github is not that effective. Is there any better way to do it?
Also, are PHP frameworks source code good to read and learn?
I think on github there is also a lot of bad written code. I can tell you that maybe working with an CMS might be something for you. While creating Plugins for CMS systems you learn the CMS itself part by part. This way you may understand why things are how they are.
In general, noone simply starts reading Code. You read Code to understand how you interact with an external system.
I am building a Flash, jQuery, and PHP based project which I would like to subversion from the get go. I have experience using Dreamweaver CS5's sub versioning capabilities. So, as far as the PHP and jQuery (the non-flash portion) goes, I'm pretty comfortable.
However, I would like some recommendations on how to subversion the Flash portion. I know Flash Builder has SVN capabilities, however, the flash portion isn't going to function as and RIA, but more, if you will, like a game. As far as my experience with Flash goes, this type of project will work best if done in Flash Professional. Here are the options, as I see them:
find an extension for Flash Professional which will enable SVN. Is there one???
create a "Flash Professional Project" in Flash Builder, built it in Flash Professional, and subversion with Flash Builder.
place my project within a defined site in Dreamweaver, and subversion from Dreamweaver.
I would like to avoid something like Tortoise SVN, as I have had more difficulty with that than I am up for for now. :)
Does anyone have any suggestions, or pointers as to how I can handle this?
Thank you for your time.
Well, any SVN client can handle any kind of file - you don't have to have an extension built into each piece of software you're using. The best way to do this is to put all of your project files into a folder somewhere and then using whatever SVN client you want just add that whole folder to your repo. Does that make sense? The front-end that you're using is more or less irrelevant.
I don't really understand what you are saying about TortoiseSVN, but since you are using different IDE's I would recommend you to use TortoiseSVN as the uniform interface to SVN. And IMO, TortoiseSVN is simple and powerful.
Man up and use the command line ;). Why SVN? Yes, I personally prefer it but there are other great alternatives, have a think about GIT, Mercurial and others too. Mercurial/Git have massive benefits for single developer projects. The flash file will be versioned just like everything else in there. Remember to set your ignore files appropriately to cut out all the os specific poop.
Soon as you get yourself a good versioning repository set up, it doesn't really matter what client you use. I like the one bundled with netbeans / versions or the cli.
I am looking for a really simple PHP image gallery system that allows file uploads and provides easy integration into any existing PHP script. I only found full galleries with database backend and templating systems for integration and the too simple ones that just take a folder with (FTP uploaded) images and show it but don't provide the possibilities for file uploads.
I'm quite close on writing my own, cause I didn't find anything yet, but I first wanted to ask if you have any suggestions.
Ok so I have a very early version of it on Github, it is under development (and not really nice yet, I just needed the admin interface up and running) but contributions and comments are welcome.
I'm working on releasing a PHP framework I have been using for a few years
on github. Been trying to read up on the most correct way a project
should be structured, what extra files such as readme's etc should be
added. Been coming up with blanks on google. Can anyone point me to a
project that's a good example or any good write ups.
Some PHP projects hosted on Git(hub) include:
CakePHP
Gallery3
Garden
PHPUnit
Kohana
I'd just make sure that no temporary files, etc. get in the repository by creating a .gitignore file, and add some readme's etc. to the root of the repository.
Any configuration files should also be ignored, and sample configuration files should be created in the repository.
I'd recommend writing the readme file in a format that Github supports, like Markdown. It'll make your repository front page look better.
You might want to follow some kind of class naming guideline to make things like autoloading easier to implement. For example, the class MyFramework_Controller should be located at directory /lib/MyFramework/Controller.php.
You should just create some kind of basic layout for now - it'll be easier to give suggestions when we can see what you have right now.